“Why Can’t Kubernetes Devs Just Add This New Feature? Seems So Easy!”
summary
KEP-driven lifecycle requires formal design, SIG buy-in, and multi-release testing, so even small ideas take years not weeks. Examples: kubectl colors issue (opened 2018, blocked by scripting, accessibility, and maintenance concerns), ephemeral containers: introduced in 1.16 and only stable in 1.25 (≈4 years, nine releases), PSP deprecated in 1.21 and removed by 1.25 after replacement work. Decisions hinge on API stability, who will maintain code, security/performance impact, and convincing multiple SIGs via the enhancements repo (KEP mandatory since 1.14).
AI-written summary · about
chapters (16)
- 0:00Welcome
- 1:28Why features take so long
- 4:38What is a KEP
- 6:03SIG meetings and discussions
- 7:48Idea to GA journey
- 10:21Adding your feature idea
- 11:05Feature proposal examples
- 11:25Network policy port range case
- 13:37Colors in kubectl case
- 15:41Debugging distroless containers case
- 18:07Pod Security Policies deprecation case
- 21:58Key takeaways
- 23:23Maintainer challenges
- 24:04Encouragement for contributors
- 26:13Renaming master to main
- 28:23Q&A
related talks
30mNavigating the Inevitable: Kubernetes Breaking Changes Behind the Scenes
20mHow Kube...
35mDeep Dive: Kubernetes (PM) SIG
22mKeynote: Backstage with Kubernetes
35mDeep Dive: Kubernetes Architecture SIG
33mA Day in the Life of Kubernetes Release with Tools, Challenges, and Operations
14mLessons from the Kubernetes Adventure
19mKeynote: Releasing a More Mature and Stable Kubernetes