The Wire · Showcase
ETCD 3.7.0 GOES LIVE ACROSS THE STACK
By RepoJournal · Filed · About Kubernetes
Kubernetes is shipping etcd 3.7.0 final across test infrastructure, kops, and the main distribution, ending months of release-candidate testing and unlocking production etcd upgrades for 1.37+.
The etcd graduation is the story tying together five major moves overnight. Kubernetes core dropped the 3.7.0-rc.0 override and bumped to final [1], kops defaulted 1.37+ to 3.7.0 while locking 1.34-1.36 on 3.6.12 [2], and test-infra purged rc.0 from sig-scalability jobs [3]. This matters because etcd 3.7.0 includes critical raft log replay fixes that were breaking control-plane bootstraps on new nodes, which kops is addressing separately by adding a configurable `storageInitializationTimeout` to give etcd-manager time to discover peers [4]. The timing is tight but intentional: teams rolling 1.37 can now do so on stable etcd. For earlier versions, stay on 3.6.12 unless you've explicitly tested 3.7.0-rc.0 in your environment. Test infrastructure also dual-published CI images to ECR [5], cutting image pull latency and costs for EKS-based testing. kops gained a second capability: custom etcd images can now be specified alongside versions for teams running internally-patched etcd [6].
Action items
- → If planning Kubernetes 1.37 upgrade, validate etcd 3.7.0 in staging first, especially control-plane node joins kubernetes/kubernetes [plan]
- → If running kops on 1.34-1.36, confirm 3.6.12 etcd is pinned and no rc.0 overrides remain in your cluster specs kubernetes/kops [plan]
- → If running sig-scalability scale tests, pull latest test-infra to pick up rc.0 cleanup kubernetes/test-infra [monitor]
References
- [1] etcd: update etcd version to v3.7.0 ↗ kubernetes/kubernetes
- [2] Default to etcd 3.7.0 for Kubernetes 1.37+ ↗ kubernetes/kops
- [3] Drop ETCD_VERSION=3.7.0-rc.0 override from sig-scalability scale jobs kubernetes/test-infra
- [4] feat(api): add storageInitializationTimeout to KubeAPIServerConfig ↗ kubernetes/kops
- [5] publish CI images to ECR as well ↗ kubernetes/test-infra
- [6] Support running custom etcd versions by setting version and image ↗ kubernetes/kops
FAQ
- What changed in Kubernetes on July 9, 2026?
- Kubernetes is shipping etcd 3.7.0 final across test infrastructure, kops, and the main distribution, ending months of release-candidate testing and unlocking production etcd upgrades for 1.37+.
- What should Kubernetes teams do about it?
- If planning Kubernetes 1.37 upgrade, validate etcd 3.7.0 in staging first, especially control-plane node joins • If running kops on 1.34-1.36, confirm 3.6.12 etcd is pinned and no rc.0 overrides remain in your cluster specs • If running sig-scalability scale tests, pull latest test-infra to pick up rc.0 cleanup
- Which Kubernetes repositories shipped on July 9, 2026?
- kubernetes/kubernetes, kubernetes/kops, kubernetes/test-infra