
Release Team Structure and Roles

How Kubernetes is Built with Kat Cosgrove
Topic 5 of 10
Published May 14, 2025 · Clip 35:32–44:34 (9:02)
Kat details the release team structure: a release lead plus sub-teams for communications (feature blogs, webinars, press), docs (enforcing documentation deadlines), enhancements (tracking KEP requirements), and release signal (watching CI and giving go/no-go calls). 20-30 people per cycle are needed, mostly shadows selected through applications. She explains that the rotating cast prevents burnout, and reflects on how all maintainers do project management regardless of title, paralleling how senior engineers at companies write less code over time.