bash: use k8s-release-dev for CI builds

[spiffxp]

What type of PR is this?

/kind cleanup

What this PR does / why we need it:

Default to community-owned gs://k8s-release-dev instead of
google.com-owned gs://kubernetes-release-dev for reading and
writing CI builds

Specifically we're modifying the default value for two bash scripts:

• push-build.sh
• packages/deb/jenkins.sh

Which issue(s) this PR fixes:

This doesn't fix, but is part of:

• Migrate jobs away from gs://kubernetes-release-dev k8s.io#846
• Migrate away from google.com GCP project google-containers k8s.io#1571

Special notes for your reviewer:

/hold
I would prefer to see kubernetes/test-infra#22840
merge first, and be able to remove /hold once I'm satisfied and
available to watch over any impact

That updates the deprecated --scenario=kubernetes_build jobs such that
they'll end up explicitly passing --bucket=kubernetes-release-dev to
push-build.sh

Does this PR introduce a user-facing change?

push-build.sh defaults to k8s-release-dev instead of
kubernetes-release-dev (https://github.com/kubernetes/k8s.io/issues/846)

[k8s-ci-robot]

@spiffxp: Adding label: do-not-merge/blocked-paths because PR changes a protected file.

Reasons for blocking this PR:

[Changes to push-build.sh will immediately affect the Kubernetes CI. This PR must be explicitly approved by SIG Release repo admins.]

• push-build.sh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[spiffxp]

/uncc @sethmccombs @mkorbi
/cc @cpanato @puerco @justaugustus @saschagrunert @xmudrii
FYI @kubernetes/release-managers

[justaugustus]

/hold
I would prefer to see kubernetes/test-infra#22840
merge first, and be able to remove /hold once I'm satisfied and
available to watch over any impact

Echoing Aaron with an explicit hold for monitoring jobs following the merge of kubernetes/test-infra#22840.

FYI @kubernetes/release-engineering @kubernetes/ci-signal @kubernetes/release-team
/lgtm
/approve

[saschagrunert]

/lgtm

[cpanato]

/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cpanato, justaugustus, saschagrunert, spiffxp

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [cpanato,justaugustus,saschagrunert]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[spiffxp]

/hold cancel
Now that kubernetes/kubernetes#103647 is out of the way, I'm ready to watch these changes go in

[spiffxp]

/retest
Neat, a GitHub API rate limit

changelog_test.go:236: 
        	Error Trace:	changelog_test.go:236
        	Error:      	Expected nil, but got: get latest GitHub tags: unable to retrieve GitHub tags: GET https://api.github.com/repos/kubernetes/kubernetes/tags?page=10&per_page=50: 403 API rate limit of 60 still exceeded until 2021-07-13 22:52:48 +0000 UTC, not making remote request. [rate reset in 20m55s]
        	Test:       	TestNewRCRelease

[liggitt]

https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/ci-kubernetes-e2e-gce-stable1-beta-upgrade-master started failing on the extract step ~4 days ago with this error:

Failed to set release from https://storage.googleapis.com/k8s-release-dev/ci/k8s-beta.txt (Unexpected HTTP status code: 404)

Are there changes required in kubernetes/kubernetes or do we need to backfill marker files to this bucket?

[liggitt]

tracking upgrade test failure in kubernetes/kubernetes#103697