Make old k8s releases also use the new registry

[afbjorklund]

Previously, we have changed all releases since 1.25 to use registry.k8s.io

Now, we also need to change any old releases to stop using k8s.gcr.io too

https://kubernetes.io/blog/2023/03/10/image-registry-redirect/

https://kubernetes.io/blog/2023/02/06/k8s-gcr-io-freeze-announcement/

The last 1.23 release on k8s.gcr.io will be 1.23.18
The last 1.24 release on k8s.gcr.io will be 1.24.12
The last 1.25 release on k8s.gcr.io will be 1.25.8
The last 1.26 release on k8s.gcr.io will be 1.26.3

---

This can be done by adding a flag to kubeadm, and by re-tagging the images.

--image-repository=registry.k8s.io

• load preloaded images from tarball

• retag k8s.gcr.io/* as registry.k8s.io/*

• to avoid having to redo all preloads

All newer releases should already be using the new registry, so mostly for 1.16-1.22

• The DefaultKubernetesRepo changed for 1.25.0 #14768

• Changing the kubeadm registry was backported #15546

The old registry is going to be deleted, so it should not be used for new installations.

• Umbrella issue: k8s.gcr.io => registry.k8s.io solution k8s.io#1834

• Sunset for k8s.gcr.io repository k8s.io#4872

[afbjorklund]

$ ~/.minikube/cache/linux/amd64/v1.23.0/kubeadm config images list --kubernetes-version=v1.23.0
k8s.gcr.io/kube-apiserver:v1.23.0
k8s.gcr.io/kube-controller-manager:v1.23.0
k8s.gcr.io/kube-scheduler:v1.23.0
k8s.gcr.io/kube-proxy:v1.23.0
k8s.gcr.io/pause:3.6
k8s.gcr.io/etcd:3.5.1-0
k8s.gcr.io/coredns/coredns:v1.8.6
$ ~/.minikube/cache/linux/amd64/v1.23.0/kubeadm config images list --kubernetes-version=v1.23.0 --image-repository=registry.k8s.io
registry.k8s.io/kube-apiserver:v1.23.0
registry.k8s.io/kube-controller-manager:v1.23.0
registry.k8s.io/kube-scheduler:v1.23.0
registry.k8s.io/kube-proxy:v1.23.0
registry.k8s.io/pause:3.6
registry.k8s.io/etcd:3.5.1-0
registry.k8s.io/coredns:v1.8.6

It's the same images.

REPOSITORY              TAG       IMAGE ID       CREATED         SIZE
registry.k8s.io/pause   3.6       6270bb605e12   18 months ago   683kB
k8s.gcr.io/pause        3.6       6270bb605e12   18 months ago   683kB

[afbjorklund]

@spowelljr @medyagh

[afbjorklund]

Re-tagging the images for airgapped installations is left to do, also needs checking china mirror for older releases.

Should also look in the cache for the old names, if not using the preload. Again, only for the affected old releases...

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.