kola/kubeadm: pull external-etcd image from MCR on ACL Azure - #23
Draft
Jiri Appl (jiria) wants to merge 1 commit into
Draft
kola/kubeadm: pull external-etcd image from MCR on ACL Azure#23Jiri Appl (jiria) wants to merge 1 commit into
Jiri Appl (jiria) wants to merge 1 commit into
Conversation
The kubeadm kola tests stand up a dedicated external-etcd node pinned to etcd v3.5.22, but the ACL image only bakes v3.5.16, so the node performs a runtime image pull. On the Azure kola pool egress to quay.io is restricted, so that pull fails, etcd never becomes healthy, and every kubeadm.* test fails at the pre-kubeadm etcd health poll. mcr.microsoft.com is reachable from the Azure pool. Add an etcd-member.service drop-in in the ACL etcd-node config that sets ETCD_IMAGE to mcr.microsoft.com/oss/v2/etcd-io/etcd:v3.5.22, so the node pulls from MCR instead of quay.io. Scoped to the ACL config only; the upstream etcd config is unchanged. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This was referenced Aug 31, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The
kubeadm.*kola tests stand up a dedicated external-etcd node pinned to etcd v3.5.22, but the ACL image only bakes v3.5.16, so the node performs a runtime image pull at boot. On the Azure kola pool egress toquay.iois restricted, so that pull fails, etcd never becomes healthy, and everykubeadm.*test fails at the pre-kubeadm etcd health poll (unable to get etcd node health). QEMU (open egress) pulls fine and passes.mcr.microsoft.comis reachable from the Azure pool and mirrors the same tags (v3.5.22,v3.5.16).Change
Add an
etcd-member.servicedrop-in in the ACL etcd-node config (etcdConfigAclWithCIDR) that sets:The etcd-wrapper resolves the image as
${ETCD_IMAGE:-${ETCD_IMAGE_URL}:${ETCD_IMAGE_TAG}}, so setting the fullETCD_IMAGEoverrides both the registry and tag in one shot — the node pulls from MCR instead of quay.io. Scoped to the ACL config only; the upstreametcdconfig is unchanged.Validation
mcr.microsoft.com/oss/v2/etcd-io/etcd:v3.5.22exists.GOOS=linux go build ./kola/tests/kubeadm/).