KCNA — CNCF Governance and Community
CNCF Governance and Community
Understanding the CNCF’s structure, governance, and project lifecycle is a key part of the KCNA exam. This topic tests your knowledge of the cloud-native ecosystem beyond just Kubernetes.
What Is the CNCF?
The Cloud Native Computing Foundation (CNCF) is a vendor-neutral foundation under the Linux Foundation. It hosts and nurtures cloud-native open-source projects.
Key facts:
- Founded in 2015
- Kubernetes was its first hosted project
- Hosts 170+ projects as of 2024
- 700+ member organizations including all major cloud providers
Project Maturity Levels
CNCF projects go through three maturity stages:
Sandbox → Incubating → Graduated
| Level | Description | Requirements |
|---|---|---|
| Sandbox | Early-stage, experimental projects | Interesting technology, active development |
| Incubating | Growing adoption, maturing | Healthy contributor base, adopted by multiple organizations |
| Graduated | Production-ready, widely adopted | Proven in production at scale, strong governance, security audits completed |
Notable Graduated Projects
| Project | Category |
|---|---|
| Kubernetes | Container orchestration |
| Prometheus | Monitoring |
| Envoy | Service proxy |
| containerd | Container runtime |
| Helm | Package management |
| Argo | GitOps / workflows |
| Flux | GitOps |
| KEDA | Event-driven autoscaling |
| Istio | Service mesh |
| Open Policy Agent (OPA) | Policy engine |
| Jaeger | Distributed tracing |
| Fluentd | Logging |
| etcd | Distributed key-value store |
| CoreDNS | DNS server |
| Linkerd | Service mesh |
Notable Incubating Projects
| Project | Category |
|---|---|
| Knative | Serverless |
| OpenTelemetry | Observability |
| Backstage | Developer portal |
| Dapr | Application runtime |
| Kyverno | Policy management |
| Cilium | Networking |
CNCF Governance Structure
┌─────────────────────────────────────────────┐
│ Governing Board │
│ (Business direction, budget, marketing) │
└──────────────────┬──────────────────────────┘
│
┌──────────────────▼──────────────────────────┐
│ Technical Oversight Committee (TOC) │
│ (Technical direction, project acceptance) │
└──────────────────┬──────────────────────────┘
│
┌──────────┼──────────┐
▼ ▼ ▼
┌─────────┐ ┌──────────┐ ┌──────────┐
│ TAGs │ │ SIGs │ │ Working │
│ │ │ │ │ Groups │
└─────────┘ └──────────┘ └──────────┘
Governing Board
- Business and marketing direction
- Budget and resource allocation
- Composed of member company representatives
Technical Oversight Committee (TOC)
- 11 elected members from the community
- Makes technical decisions about project acceptance and lifecycle
- Defines project maturity criteria
- Reviews projects for graduation
TAGs (Technical Advisory Groups)
TAGs provide cross-project guidance on specific topics:
| TAG | Focus Area |
|---|---|
| TAG Security | Security best practices |
| TAG Network | Networking standards |
| TAG Runtime | Container runtimes |
| TAG App Delivery | Application delivery |
| TAG Observability | Monitoring, logging, tracing |
| TAG Storage | Storage standards |
| TAG Environmental Sustainability | Green computing |
| TAG Contributor Strategy | Growing contributors |
SIGs (Special Interest Groups)
SIGs focus on specific areas within individual projects. Kubernetes has many SIGs:
| Kubernetes SIG | Focus |
|---|---|
| SIG Network | Networking in Kubernetes |
| SIG Storage | Storage in Kubernetes |
| SIG Auth | Authentication and authorization |
| SIG Node | Node agent (kubelet) |
| SIG Scheduling | Pod scheduling |
CNCF Landscape
The CNCF Cloud Native Landscape is a comprehensive map of the cloud-native ecosystem.
Categories include:
- App Definition & Development — databases, streaming, messaging
- Orchestration & Management — scheduling, service mesh, API gateway
- Runtime — container runtimes, storage, networking
- Provisioning — automation, security, key management
- Platform — PaaS, serverless
- Observability & Analysis — monitoring, logging, tracing
You can explore it at: landscape.cncf.io
CNCF Trail Map
The CNCF Trail Map provides a recommended path for adopting cloud-native technologies:
- Containerization — Start with containers
- CI/CD — Automate your pipeline
- Orchestration — Use Kubernetes
- Observability — Add monitoring and logging
- Service Mesh — Manage service-to-service traffic
- Networking & Policy — Network policies and security
- Distributed Database — Stateful workloads
- Messaging — Async communication
- Container Registry — Store container images
- Software Distribution — Distribute to edge/customers
Contributing to CNCF Projects
The CNCF community is open to contributors at all levels:
| Contribution Type | Examples |
|---|---|
| Code | Bug fixes, features, tests |
| Documentation | Tutorials, API docs, translations |
| Community | Answering questions, organizing meetups |
| Testing | Bug reports, test cases |
| Design | UX/UI improvements, architecture reviews |
KCNA Exam Tips
- Know the three maturity levels: Sandbox → Incubating → Graduated
- Be able to identify which major projects are Graduated (Kubernetes, Prometheus, Envoy, Helm, Argo, containerd)
- Know the role of the TOC — technical direction and project lifecycle decisions
- Understand the difference between TAGs (cross-project) and SIGs (within a project)
- The CNCF Landscape organizes the cloud-native ecosystem by category
- The Trail Map shows the recommended adoption path
What’s Next?
Test your knowledge of cloud-native architecture with practice questions.
