SIG Release Deep Dive
summary
SIG Release explains how the project keeps a “covenant of trust” by running a disciplined release pipeline: quarterly three-month cadence releases, a defined release lead/branch manager rotation, and a heavy push to automation. Builds move from Onaga into cloud-based GCB_MGR (Google Container Builder Manager) and CI runs on prow/testgrid; 117 people coordinate triage, docs, and cut binaries. The last month gets intense (daily meetings, ~5–10 hours/week for leads); many manual steps still remain despite the tooling.
AI-written summary · about
chapters (11)
- 0:00Start
- 0:33Overview
- 3:01Provide Opportunities for New Contributors
- 3:26Release Policy
- 5:02Summary of the Release Process
- 16:04Google Container Builder Manager
- 22:59Branch Diff
- 25:00What Is the Time Commitment for a Release Lead
- 27:19Dashboards
- 34:41What Are the Things That Software Engineers Could Do To Improve this Process
- 35:28Scalability Testing
related talks
38mSIG Release - Deep Dive: Release Engineering Subproject
32mDeep Dive: Kubernetes (Release) SIG
35mIntro: Kubernetes (Release) SIG
19mReleasing Kubernetes Less Often and More Secure – The SIG Release Update
33mSIG Architecture Intro and Update
36mDeep Dive: SIG Release
27mKubernetes SIG Architecture Intro and Updates
37mSIG Architecture Intro and Update
