e2e: build kind node images instead of pulling prebuilt kindest/node
#6 033 ouverte le 27 mai 2026
Métriques du dépôt
- Stars
- (723 étoiles)
- Métriques de merge PR
- (Métriques PR en attente)
Description
Our e2e tests currently depend on prebuilt kindest/node images being published for the exact Kubernetes version we target. This creates a recurring pain point: when we bump Kubernetes (e.g. to v1.34.8), the matching kindest/node image often doesn't exist yet, breaking CI.
We had to work around this in #5857 by pinning the management cluster to an older kind image (v1.34.3) while using v1.34.8 for workload clusters.
Proposal
Switch to building kind node images with kind build node-image <version> instead of relying on prebuilt kindest/node images. As noted in kubernetes-sigs/kind#4157 (comment: https://github.com/kubernetes-sigs/kind/issues/4157#issuecomment-4555966335), this is not more expensive than pulling a prebuilt image, either way you download a tarball of k8s binaries + the base image layer.
This would allow us to use the same Kubernetes version for both management and workload clusters, and avoid breakage when kindest/node images lag behind Kubernetes releases.