-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
migrate usage of "gcr.io/kubernetes-ci-images" #4103
Comments
@neolit123: Please ensure the request meets the requirements listed here. If this request no longer meets these requirements, the label can be removed In response to this:
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. |
/good-first-issue |
@fabriziopandini: Please ensure the request meets the requirements listed here. If this request no longer meets these requirements, the label can be removed In response to this:
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. |
On top of I suggest changing also in the same PR (or in separate PR if you prefer) |
Hi @fabriziopandini. Can I work on this ? |
/assign |
looks like the new GCS bucket doesn't have the latest artifacts: |
Detailed Description
as part of migrating the k8s google infra to community maintained the GCR bucket "gcr.io/kubernetes-ci-images"
is being renamed to "gcr.io/k8s-staging-ci-images".
kubernetes/k8s.io#1460
we already applied this change to kubeadm, but a search revealed that CAPI has it in a few places, including :
/kind feature
/priority important-soon
(this change will happen in the 1.21 cycle)
/help
if someone wants to help with the cleanup.
The text was updated successfully, but these errors were encountered: