---
# System prepended metadata

title: Future k8s.gcr.io redirect to registry.k8s.io

---

# Future k8s.gcr.io redirect to registry.k8s.io

TLDR: Sometime, a month or more from now, k8s.gcr.io may proxy or 302 redirect to registry.k8s.io. In most cases no end-user changes are required.

#sig-k8s-infra has been working to reduce the cost of distributing Kubernetes to the world. Our new registry.k8s.io is in production and k8s 1.25 tooling will pull images from there.

However, all prior releases will continue to pull from k8s.gcr.io for many years to come at great cost.

We are working with the Google Container Registry team to possibly 302 redirect or proxy so our cost savings can be fully realized.

Due to the changes in retrieval of Kubernetes, we wanted to notify the community at least 30 days in advance. This change will not occur until October 1st or later (if at all).

There should be no issues unlessthe 302 directed urls are inaccessible from your cluster / deployment.