-
Notifications
You must be signed in to change notification settings - Fork 821
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
[Umbrella Issue] Migrate K8s projects from k8s.gcr.io -> registry.k8s.io #4738
Comments
I believe kubernetes-sigs/release-notes can be ignored/marked as complete. All references to k8s.gcr.io are from previous release notes and valid references. |
There's also kubernetes/website#39353 |
there's a couple staging repos listed that should not be modified directly, but instead should be fixed within the kubernetes/kubernetes repo:
|
Thanks for the clarity @liggitt ! |
I'll update the list re:staging repos |
kubernetes-sigs/kind search results are false positives:
There will be many similar instances. For test data it would be OK to update to registry.k8s.io. The mirror config like this should stay, however. |
This should probably turn into a series of issues like kubernetes/test-infra#28665 linking back here so repo owners can handle them with local context. Some of them won't be good first issue, some will. |
Agreed, especially for the bigger ones like k/k. |
|
xref: #4872 |
Thanks @xmudrii I've updated the parent issue with links to the PRs 👍 |
kubernetes/test-infra is done in kubernetes/test-infra#28985 The remaining references will not be removed until we flip github.com/kubernetes/k8s.io to only publish to registry.k8s.io and re-arrange the manifests etc. A full listing of remaining references and why they're there is in the PR body. |
@mrbobbytables I did another run through the checklist. kubernetes-sigs/cluster-proportional-vertical-autoscaler is done. I'm also following up on k/docs. |
thanks @xmudrii |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
@mrbobbytables @BenTheElder @Riaankl Should we consider this as done given that almost all repos are migrated or should we do another round of checks to be sure? |
I think we can, any issues should have bubbled up by now 👍 thanks for checking in. /close |
@mrbobbytables: Closing this issue. 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. |
With the change to defaulting to registry.k8s.io as our image registry and the planned freeze in April, projects within the Kubernetes orgs should update their image references to point to the new address.
Below is a list of repos that were surfaced in a "dumb" search for k8s.gcr.io, there may be valid references or false positives and they should be checked more closely.
NOTE: We can ignore references to staging-k8s.gcr.io, but any other references to k8s.gcr.io should be updated to registry.k8s.io
Repos with k8s.gcr.io found in search
registry.k8s.io
kubernetes-sigs/secrets-store-csi-driver#1161The text was updated successfully, but these errors were encountered: