
KEP Process and Feature Release Lifecycle

How Kubernetes is Built with Kat Cosgrove
Topic 6 of 10
Published May 14, 2025 · Clip 44:34–52:04 (7:30)
Kat explains how features get into Kubernetes: contributors open a KEP in the enhancements repo, the owning SIG discusses it publicly on GitHub or Slack, and if approved with SIG lead opt-in, the feature must hit deadlines (code freeze, docs freeze, test freeze) across a 14-week cycle. Features graduate through alpha (off by default, feature flag), beta (on by default, flag can disable), and GA (on by default, no flag). She shows the documented feature gates on screen and emphasizes that Kubernetes documents everything to avoid tribal knowledge, encouraging other projects to borrow these practices at their own scale.