Ensuring Quality in Kubernetes: The Graduation Process From Alpha To GA
Talkat KubeCon + CloudNativeCon Europe 2025 · on Friday, 2025-04-04· at 11:00· Platinum Suite | Level 3 | Room 1-2·
summary
Kubernetes enforces graduation with concrete steps: CI runs use Ginkgo v2 labels and the centralized feature registry to select tests, CI presubmit aims for ~1 hour and release-blocking for ~2 hours, while scale tests can run 5,000-node clusters taking 12–14 hours. Dynamic Resource Allocation (DRA) tests require a mock driver on kind clusters and explicit feature-gate metadata; PRs now block if an alpha is on by default. The project also enforces a zero flake policy and uses triage.k8s.io to cluster and file flaky-test bugs.
AI-written summary · about
chapters (16)
- 0:00Kubernetes quality and graduation
- 1:22Feature development and CAPs process
- 3:07Alpha beta and GA stages
- 4:52Kubernetes APIs and their role
- 7:01Challenges in beta API graduation
- 8:25Production readiness and SIG release
- 9:50Testing infrastructure and conformance
- 12:46SIG testing’s role and responsibility
- 13:29Dynamic Resource Allocation testing
- 16:20GKE labels and metadata improvements
- 19:09New CI standards for testing
- 21:15Enforcing alpha feature defaults
- 23:19Tooling for contributors
- 24:42Stability from alpha to GA
- 27:21Zero flake policy
- 30:53Cultural shift for stable CI
related talks
20mCongratulations, Kubernetes!
14mLessons from the Kubernetes Adventure
33mA Day in the Life of Kubernetes Release with Tools, Challenges, and Operations
26mKubernetes SIG Apps Updates
18mKubernetes Project Update
43mKubernetes: Use it, Contribute to it, and Enjoy it!
42mGuide Us on Next Steps in Kubernetes Device Manage...
35mLeveling Up Your CD: Unlocking Progressive Delivery on Kubernetes