Kubernetes 1.27 Registry change

Hello folks,

here is the crazy swabian?#Kubernetes?guy and I want to give you in my series some tipps about Kubernetes.

As you know, there have been some serious changes in the update of Kubernetes 1.27.

One of them is a new registry address.

The previous k8s.gcr.io has been changed to registry.k8s.io.

This may have a major impact on Kubernetes clusters. Especially in very customized clusters like "Airgap" this can have fatal consequences, because then no more changes can be pulled from the "old" registry.

?Please update your manifests as soon as possible to point to registry.k8s.io.

Numerous Kubernetes subprojects host their images there as well.

?

Now how can I verify this?

You can use the following command to check which images are affected:

??kubectl get pods --all-namespaces -o jsonpath="{.items[*].spec.containers[*].image}" |\
tr -s '[[:space:]]' '\n' |\
sort |\
uniq -c        

Another possibility would be, if the permission in the cluster allows it, to install a kubectl - plugin:

it is called "community-images", that will scan and report any images using the k8s.gcr.io endpoint.

You can generate a report with:

kubectl community-images