-
Notifications
You must be signed in to change notification settings - Fork 505
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
[VDF] anago: Publish container images on K8s Infra (k8s-staging-kubernetes) - take two #1230
Conversation
@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
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
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
@listx how are things looking for retrying to cutover? |
From #270 (comment):
|
afe80c4
to
4697e8f
Compare
@listx has kicked off the VDF again today, so it's time to move this PR forward. I'm running some test releases against this PR... EDIT: Needed to re-run the mock stage, as the new k8s-cloud-builder image had not yet been built --> https://console.cloud.google.com/cloud-build/builds/6f98c551-6a0a-42b3-8adb-577737e98cb3?project=kubernetes-release-test |
(for anybody watching, we're on hold again...) |
Next VDF attempt is this Monday, 7/20. I've opened kubernetes/k8s.io#1042 for this. |
The existing check is causing issues on the new registry. This temporarily disables the write check until the vanity domain flip is successfully complete. Signed-off-by: Stephen Augustus <saugustus@vmware.com>
@kubernetes/release-engineering -- Promotion for a mock stage/release against this PR was proven out in kubernetes/k8s.io#1047. Squashed, rebased, and ready for approval. /hold cancel |
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: cpanato, hasheddan, justaugustus, saschagrunert 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 reverts commit b60c168, reversing
changes made to 2614864.
/assign @tpepper @saschagrunert @cpanato @hasheddan
cc: @kubernetes/release-engineering
/priority critical-urgent
Special notes for your reviewer:
Reapplies #1199, which was partially reverted in #1229.
/hold until @listx kicks the cutover again next week
Does this PR introduce a user-facing change?