How the Kubernetes k8s.gcr.io redirect impacts GKE and Anthos

[ad_1]

In November 2022, the open supply Kubernetes undertaking introduced that its new picture registry, registry.k8s.gcr.io, was formally GA. The brand new registry would exchange the legacy k8s.gcr.io registry, with k8s.gcr.io getting no additional updates after April three, 2023. To help on this transition and make sure that customers of earlier Kubernetes releases and tooling can replace to supported variations in time, the Kubernetes undertaking, in partnership with Google, step by step began redirecting picture requests from k8s.gcr.io to registry.k8s.io on March 20, 2023.

Right this moment’s put up covers what’s taking place, why, and, extra importantly, what actions you’ll be able to take to change to registry.k8s.io to mitigate future points.

Why is Kubernetes switching to the brand new registry?

Google open sourced the Kubernetes undertaking and has supported the Cloud Native Computing Basis (CNCF) since its inception. Right this moment, there are hundreds of thousands of customers and an enormous, world ecosystem of distributors and tasks that assist the undertaking and the CNCF. registry.k8s.io, the brand new vendor-agnostic registry constructed by Kubernetes neighborhood members from Google, Amazon, VMware, and elsewhere creates a world CDN for the undertaking’s container pictures, spreading the load throughout a number of cloud suppliers. This new registry is extra sustainable for the undertaking and supplies a greater expertise for all Kubernetes customers.

For added info on the registry, see the Kubernetes Group Weblog put up about its launch.

Why redirect requests?

The redirect is a momentary measure to easy the transition to registry.k8s.io. Clusters mustn’t proceed to depend on k8s.gcr.io in the long run; the Kubernetes neighborhood plans to sundown it sooner or later.

The excellent news is that registry.k8s.io is a mirror of k8s.gcr.io that may be dropped in as a direct substitute for many customers. Nevertheless, for those who use Google Kubernetes Engine (GKE) or Anthos in a restricted atmosphere that applies strict area identify or IP deal with entry insurance policies, akin to with VPC Service Controls, and also you depend on Kubernetes neighborhood pictures from k8s.gcr.io, it’s possible you’ll be impacted and have to make some changes to be future-compatible.

What cluster configurations are impacted by the redirect?

Workloads which may be impacted are those who run on high of GKE and Anthos clusters working in a restricted atmosphere that applies strict area identify or IP deal with entry insurance policies through the use of VPC Service Controls or different community entry tooling.