Open Source Governance and the Kubernetes Community

Most people who use Kubernetes have never read a KEP, attended a SIG meeting, or looked at the contributor ladder. They treat the project like a product: somebody else builds it, you consume it. That works until you need to understand how the project actually runs. Three releases a year, over twenty SIGs across dozens of companies, hundreds of enhancement proposals per cycle. That output does not happen by accident.

The KCNA tests this under the Cloud Native Architecture domain (12% of the exam). The questions focus on governance structures, not memorization: how the project organizes decision-making through SIGs, how changes move from idea to stable feature through KEPs, how contributors advance through a defined membership ladder, how the release cycle operates on a predictable cadence, and what the CNCF maturity levels mean for adopters evaluating projects.