How Kubernetes Works: Community, Velocity and Contribution
Talkat Open Source Leadership Summit 2017 · on Wednesday, 2017-02-15· at 09:45· Grand Sierra Ballroom·
summary
Kubernetes claims >43,000 commits, >1,500 unique contributors and ~20,000 stars while moving from Google-led work to a broad community; growth delivers rapid feedback but costs huge coordination and time. The project builds concrete primitives: kubeadm for cluster install, a public features repo as the backlog, and cross-company SIGs that own areas; releases follow a 2.5–3 month cadence with burndown meetings and retrospectives to gate quality. Challenges remain: GitHub scaling, review load and cross-SIG dependencies.
AI-written summary · about
chapters (11)
- 0:00Start
- 3:41Community Growth
- 4:21Community Composition
- 4:57Open Engagement
- 6:21Open Community, not just Open Source
- 7:25Costs and challenges
- 9:49What makes it work?
- 10:39Special Interest Group (SIG)
- 13:23Transparency
- 16:42Roadmap
- 19:22Ownership
