How Kube...
summary
Kubernetes ships three releases a year and feature decisions live in KEPs (look up KEP 1287 for in‑place pod resize to see API changes, SIGs involved, and stage history), while SIGs and subprojects own code and can release independently; track stable/beta/alpha via kep.k8s.io and the release changelog, file bugs under kubernetes/kubernetes (expect eight required fields) or email security@kubernetes.io for vuln reports, follow Last Week in Kubernetes Development and Wisdom of the Cloud, and join Slack or SIG meet‑and‑greets to start contributing.
AI-written summary · about
chapters (8)
- 0:00Kubernetes governance
- 2:07CNCF and SIGs roles
- 4:35Proposing features via KEPs
- 6:39Tracing feature history with KEPs
- 9:09Reporting Kubernetes bugs
- 11:16Kubernetes news updates
- 14:02Subscriptions for operators
- 16:08Contributing to Kubernetes
related talks
35mIntro: Kubernetes (Release) SIG
32mDeep Dive: Kubernetes (Release) SIG
30mNavigating the Inevitable: Kubernetes Breaking Changes Behind the Scenes
32mIntro: SIG Release
36mDeep Dive: SIG Release
34m“Why Can’t Kubernetes Devs Just Add This New Feature? Seems So Easy!”
33mA Day in the Life of Kubernetes Release with Tools, Challenges, and Operations
35mKubernetes SIG CLI: Intro And Updates