Add registry.k8s.io/etcd as an official mirror

[hakman]

With #19798, etcd images are also being pushed to registry.k8s.io/etcd.
registry.k8s.io/etcd and, eventually, become the main mirror.

CC @ahrtr @joshjms

[ahrtr]

thx for you all driving the effort.

It's Ok for me to add registry.k8s.io/etcd into the release template, see example https://github.com/etcd-io/etcd/releases.

Currently gcr.io/etcd-development/etcd serves as the primary registry, and quay.io/coreos/etcd as secondary. We can add registry.k8s.io/etcd into the secondary list as well.

It seems that our release script hasn't been updated yet to automatically pushing image to registry.k8s.io/etcd.

• https://github.com/etcd-io/etcd/blob/release-3.6/scripts/release.sh

[hakman]

We can add registry.k8s.io/etcd into the secondary list as well.

Sounds good to me.

It seems that our release script hasn't been updated yet to automatically pushing image to registry.k8s.io/etcd.

Publishing to registry.k8s.io/etcd can only be done via PR. At the moment it also need an additional push to a staging registry, which may be skipped if kubernetes/k8s.io#8596 is accepted.

[ahrtr]

No, once the PR is merged, you won't need to push to gcr.io/k8s-staging-etcd before doing the PR for publishing to registry.k8s.io/etcd. I will just consider gcr.io/etcd-development as the staging registry.

I was trying to understand the existing workflow.

[hakman]

In the existing workflow, someone or some job needs to push the images to gcr.io/k8s-staging-*.
Once this happens, they can be published via a PR to kubernetes/k8s.io to registry.k8s.io.

[ahrtr]

someone or some job needs to push the images to gcr.io/k8s-staging-*.

Is it done by a PR/job something like kubernetes/kubernetes#131105?

[hakman]

Yes

[ahrtr]

thx for the clarification. It's clear now.