etcd in 2026: Enhancements, V3.7 Roadmap...
summary
etcd v3.7 delivers concrete changes: range stream sends chunks so a 5,000-key (~500 MB) range drops from ~160 ms to ~88 ms in the demo, and keys-only optimization reads keys from the in‑memory index without touching disk. v2 store is fully removed and upgrade requires documented step‑up versions (example path: 3.5.19 → 3.5.21 → 3.6). The etcd Operator (0.2/0.3) already handles TLS, member add/remove, patch upgrades and CR status; moving from StatefulSet to pods and backup/restore storage spec are planned.
AI-written summary · about
chapters (16)
- 0:00SIGCD and speakers intro
- 1:06What is etcd in Kubernetes
- 2:34etcd 3.7 highlights
- 4:45Range query streaming
- 5:29Keys-only optimization
- 6:33V2 to V3 storage
- 8:19Lease expiry cleanup
- 9:01Unix socket and JWT
- 10:31Breaking changes in 3.7
- 12:20etcd operator intro
- 14:08etcd operator features
- 16:18etcd operator demo
- 24:23etcd operator future
- 27:32Contributing to etcd
- 28:57Mentorship programs
- 29:47Q&A
related talks
32metcd V3.6.0 and etc...
32mSIG etcd Maintainer Track Talk
36mWhat You Should Know about Etcd v3
42metcd: distributed locking and service discovery
19mDr etcd; or; How I Learned to Stop Worrying and Love the Datastore - Nick Young, VMware
05mLet’s Deploy etcd Operator
28mHow CoreOS sees the container industry
23mThe Secret Recipe of etcd