-
Notifications
You must be signed in to change notification settings - Fork 520
[VDF] Partial revert of k8s.gcr.io cutover #1229
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
This partially reverts commits: - 29b8e1d - 4343e86 - dcaf5c0 From Linus: "We found a hard-coded internal reference that we had missed which caused some large fraction of traffic from certain regions to be sent to the wrong place. Because it is Friday afternoon, we will halt the rollout, do a fast rollback, and try again early next week. Sorry!" Signed-off-by: Stephen Augustus <[email protected]>
@justaugustus: Adding label: Reasons for blocking this PR:[Changes to certain release tools can affect our ability to test, build, and release Kubernetes. This PR must be explicitly approved by SIG Release repo admins.] 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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: hasheddan, justaugustus 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:
Approvers can indicate their approval by writing |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
This partially reverts commits:
From @listx on k-dev:
Signed-off-by: Stephen Augustus [email protected]
/assign @tpepper @hasheddan @saschagrunert @cpanato
cc: @kubernetes/release-engineering
/priority critical-urgent
Special notes for your reviewer:
I've kept the manifest validation logic in here from #1199 and only reverted the project/bucket changes.
Does this PR introduce a user-facing change?