Mechanics of releasing a large project: Leadership learnings from Kubernetes releases
summary
Kubernetes runs ~4‑month release cycles with ~40 distributed contributors, handling ~1,000 issues per cycle from a repo with ~100k issues/PRs; builds and signs binaries and container images via Google Cloud Build using krel, stages artifacts then promotes them with kpromo, and gates releases on testgrid master‑blocking and conformance dashboards. Cadence is three releases/year with 12‑month support and monthly patches. Operational practices include asynchronous communication, lazy consensus windows (3–14 days), strict timelines, and deliberate delegation and deferral to keep releases on schedule.
AI-written summary · about
chapters (9)
- 0:00Kubernetes release leadership
- 1:35Release team structure
- 6:29Release process overview
- 9:18Release tooling with Krel
- 12:26Release cadence policies
- 13:29Large project release challenges
- 15:59Leadership learnings
- 18:26Contributing to SIG Release
- 19:14Q&A
related talks
26mAre We There Yet? My Experience Leading a Kubernetes Release Team
06mParticipating In The Kubernetes Release Team
22mKeynote: Backstage with Kubernetes
36mGuidelines for Achieving Project Release Maturity
38mSIG Release Deep Dive
33mState of Kubernetes Contributor Community
38mSIG Release - Deep Dive: Release Engineering Subproject
13mSlow Down: Releasing Deliberately