Hey there all,
You may have seen some of the blog posts / discussions on the move to registry.k8s.io, there are some actions we need to take to make sure that all our projects are compatible moving forward.
You MUST update references from k8s.gcr.io to registry.k8s.io by April 3rd
References to staging-k8s.gcr.io are placeholder addresses that don’t NEED to be replaced, but probably should to match the new default.
See this tracking issue to see if your repo contains references that need to be updated (there are about 60 remaining at the time of this email)
If you or your employer reference k8s.gcr.io, consider mirroring the registry or updating to point to the new address.
We introduced the new registry that can federate requests to multiple cloud providers last year towards the end of the 1.25 release. k8s.gcr.io was a custom Google Container Registry (GCR) domain that was set up solely for the Kubernetes project. This has worked for many years, but to reduce our egress costs and spread the load between multiple providers, we deployed registry.k8s.io.
This change doesn’t just impact end users, but ourselves as well. We did a “dumb” search for instances of k8s.gcr.io across all our orgs and found 85 repos containing references to the old registry. Some of these are valid references or can be ignored, but we still need folk to check, and if applicable update them.
If you have questions or concerns, please reply here, reach out in the #sig-k8s-infra channel or send an email to their mailing list.
To unsubscribe from this group and stop receiving emails from it, send an email to leads+un...@kubernetes.io.