-
Notifications
You must be signed in to change notification settings - Fork 280
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
[Action Required] Update references from k8s.gcr.io to registry.k8s.io #3324
Comments
@mrbobbytables Can you assign this issue to me, as I am a beginner to CNCF contribution? /assign |
@nikzayn I'm not an owner of this repo, I will leave triage to the maintainers of it. |
Sure thing, I want to ask one thing this issue remarks that all references of k8s.gcr.io should be updated to registry.k8s.io. Why do we need to add this change, can you explain in brief or helpful links that I can refer to? |
The blog posts linked in the issue explain it all 👍 |
Update references from k8s.gcr.io to registry.k8s.io [#3324]
…3329-to-release-1.25 [release-1.25] Update references from k8s.gcr.io to registry.k8s.io [#3324]
…3329-to-release-1.23 [release-1.23] Update references from k8s.gcr.io to registry.k8s.io [#3324]
…3329-to-release-1.24 [release-1.24] Update references from k8s.gcr.io to registry.k8s.io [#3324]
…3329-to-release-1.26 [release-1.26] Update references from k8s.gcr.io to registry.k8s.io [#3324]
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.
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
k8s.gcr.io search results
ref: [Umbrella Issue] Migrate K8s projects from k8s.gcr.io -> registry.k8s.io
/kind cleanup
/priority important-soon
The text was updated successfully, but these errors were encountered: