🌱 Update references from k8s.gcr.io to registry.k8s.io #60
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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