etcd
v3.5.29Kubernetes Coreetcd v3.5.29 is a maintenance release on the 3.5 branch with no detailed changelog published in the release notes themselves.
enhancementCheck CHANGELOG-3.5.md before upgrading
The release notes here are skeletal — no specific fixes or changes are listed. Before upgrading any etcd cluster, pull up CHANGELOG-3.5.md on the etcd GitHub repo and filter for v3.5.29 entries. Patch releases on 3.5 typically carry bug fixes and CVE patches that aren't always obvious from the version bump alone.
breakingReview the official upgrade guide even for patch releases
The release explicitly calls out that breaking changes may exist even in 3.5.x patch versions. Don't skip the upgrade guide. Test in a staging environment first, especially if you're running etcd as the backing store for Kubernetes — a botched etcd upgrade can take down your entire control plane.
securityVerify container image source after upgrade
If you pull etcd images in CI/CD pipelines, confirm you're pointing to gcr.io/etcd-development/etcd as the primary registry. The quay.io mirror is secondary and may lag. Pin to the exact digest rather than the floating tag to avoid supply chain risk.
Key changes (4)
- Maintenance/patch release on the stable 3.5 branch
- Full change details require consulting the CHANGELOG-3.5.md directly
- Container images available on gcr.io/etcd-development/etcd (primary) and quay.io/coreos/etcd (secondary)
- Upgrade guide should be reviewed before upgrading due to potential breaking changes