Add etcd 3.6.6 publish images

[yashsingh74]

Added the etcd 3.6.6 sha for publish

Ref: https://console.cloud.google.com/artifacts/docker/etcd-development/us/gcr.io/etcd

[yashsingh74]

cc: @ahrtr @joshjms @hakman @ivanvc

[ahrtr]

I don't see the 3.6.6 images in gcr.io/k8s-staging-etcd/etcd yet.

@joshjms @hakman did you manually push the images previously? Does it require any permission?

[ahrtr]

I think we need to add 3.6.6-0 as well. cc @joshjms @hakman

[joshjms]

We can use the digest from our gcr.io registry to promote that image to registry.k8s.io immediately.

[joshjms]

➜  ~ crane digest gcr.io/etcd-development/etcd:v3.6.6         
sha256:60a30b5d81b2217555e2cfb9537f655b7ba97220b99c39ee2e162a7127225890

lgtm 😄

[ahrtr]

I know that the digests do not change.

But gcr.io/etcd-development/etcd and gcr.io/k8s-staging-etcd/etcd are two different registries. I only see the etcd 3.6.6 images in the former, not the latter.

Isn't this a problem?

[joshjms]

Ohh nope it's not a problem, gcr.io/etcd-development is already added as a source registry here 22cf2aa so we don't need to push it to k8s-staging-etcd

[ahrtr]

Got it, thx for the clarification.

[ahrtr]

Reference: #8344

[joshjms]

➜  ~ crane digest gcr.io/etcd-development/etcd:v3.6.6         
sha256:60a30b5d81b2217555e2cfb9537f655b7ba97220b99c39ee2e162a7127225890

lgtm 😄

[joshjms]

/hold

[joshjms]

/unhold

[ahrtr]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ahrtr, joshjms, yashsingh74

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• registry.k8s.io/images/k8s-staging-etcd/OWNERS [ahrtr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[bzsuni]

https://prow.k8s.io/view/gs/kubernetes-ci-logs/pr-logs/pull/135271/pull-kubernetes-e2e-kind/1991394355570544640

Failed to pull registry.k8s.io/etcd:3.6.6-0 with error: command "docker exec --privileged kind-build-1763620611-173758150 ctr --namespace=k8s.io content fetch --platform=linux/amd64 registry.k8s.io/etcd:3.6.6-0" failed with error: exit status 1
time="2025-11-20T06:36:54Z" level=info msg="fetch failed after status: 404 Not Found" host=registry.k8s.io
ctr: failed to resolve reference "registry.k8s.io/etcd:3.6.6-0": registry.k8s.io/etcd:3.6.6-0: not found
Retrying registry.k8s.io/etcd:3.6.6-0 pull after 1s ...
Image build Failed! Failed to pull Images: command "docker exec --privileged kind-build-1763620611-173758150 ctr --namespace=k8s.io content fetch --platform=linux/amd64 registry.k8s.io/etcd:3.6.6-0" failed with error: exit status 1
ERROR: error building node image: command "docker exec --privileged kind-build-1763620611-173758150 ctr --namespace=k8s.io content fetch --platform=linux/amd64 registry.k8s.io/etcd:3.6.6-0" failed with error: exit status 1

Image registry.k8s.io/etcd:3.6.6-0 not found, what should I do to solve this? @joshjms

[ahrtr]

Image registry.k8s.io/etcd:3.6.6-0 not found, what should I do to solve this? @joshjms

It's because the tag 3.6.6-0 wasn't added in #8769 (comment).

I think we can use v3.6.6 for Kubernetes workflow, but it might be a problem for Kubeadm. cc @joshjms @hakman @neolit123

[neolit123]

I think we can use v3.6.6 for Kubernetes workflow, but it might be a problem for Kubeadm. cc @joshjms @hakman @neolit123

as long as the image exists in the registry and the kubeadm constants file is set to use it, it would work.