[Action Required] Update references from k8s.gcr.io to registry.k8s.io #2231
Labels
kind/cleanup
Categorizes issue or PR as related to cleaning up code, process, or technical debt.
priority/important-soon
Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
sig/scalability
Categorizes an issue or PR as relevant to SIG Scalability.
Comments
Closed
85 tasks
ameukam
added a commit
to ameukam/perf-tests
that referenced
this issue
Feb 14, 2023
Reference issue: - kubernetes#2231 Part of: - kubernetes/k8s.io#4738 Signed-off-by: Arnaud Meukam <ameukam@gmail.com>
|
@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. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
/sig scalability
/priority important-soon
The text was updated successfully, but these errors were encountered: