Are We There Yet? My Experience Leading a Kubernetes Release Team
Talkat KubeCon + CloudNativeCon North America 2019 · on Wednesday, 2019-11-20· at 17:20· Room 16AB - San Diego Convention Center, Mezzanine Level·
summary
9-month journey that goes from 9 months and 3 releases to running the 1.15 cycle: leads manage a fully distributed volunteer team via Slack, GitHub, Zoom and YouTube, use Prow and TestGrid for CI, and rely on SIGs for QA. Release work includes enforcing mandatory enhancement proposals (KEPs) from 1.14, iterating roles (emeritus advisor added), scaling the shadow program (from 49 to 70 signups), and shipping a release delayed two days for failing scalability tests.
AI-written summary · about
chapters (14)
- 0:00Intro
- 1:54Before we start
- 3:30What is the K8s Release Team?
- 6:41My Experience on the K8s Release Team
- 7:58My Journey on the Kubernetes Release Team
- 10:04What is interesting about the K8s Release Team
- 11:30Rotating Release Team
- 12:58Decision Making
- 15:07Few things block a K8s release
- 16:56Iterating: Shadow Program
- 18:25Iterating: Role Changes
- 19:51Introducing KEPS
- 22:16Kubernetes values = the release team
- 24:39Questions
related talks
27mMechanics of releasing a large project: Leadership learnings from Kubernetes releases
31mKubernetes SIG Contributor Experience: A Look Back, a Step Forward
04mScaling teams with technology
40mThe Accidental Maintainer: Sideways Stories Into Open Source Leadersh...
29mIntro: SIG PM (Kubernetes)
35mDeep Dive: Kubernetes (PM) SIG
29mGuiding Kubernetes: The Steering Committee's Role in Project Evolution
27mIntro: Kubernetes (PM) SIG