KCNA — Cloud Native Landscape
Cloud Native Landscape
The CNCF hosts hundreds of open-source projects that form the cloud-native ecosystem. The KCNA exam expects you to understand how this landscape is organized and which tools fall where.
What Is the CNCF Landscape?
The CNCF Landscape is a map of every major cloud-native tool, organized by category. You can explore it at landscape.cncf.io.
It covers:
- Container runtimes
- Orchestration and scheduling
- Networking and service mesh
- Observability and monitoring
- CI/CD and application delivery
- Security
- Storage
- And many more categories
Exam note: You do NOT need to memorize the entire landscape. You need to know the major graduated projects and understand the project maturity model.
CNCF Project Maturity Levels
Every CNCF project goes through a maturity process:
| Level | What It Means | Example Projects |
|---|---|---|
| Sandbox | Early-stage, experimental. Not production-ready. | OpenKruise, Carina |
| Incubating | Growing adoption. Production-used by some companies. | Argo, gRPC, KubeVirt |
| Graduated | Widely adopted. Production-proven. Considered stable. | Kubernetes, Prometheus, Envoy |
How Maturity Works
Sandbox → Incubating → Graduated
(New) (Growing) (Mature)
- A project enters Sandbox to get CNCF visibility and support
- After demonstrating adoption and community growth, it moves to Incubating
- After proving production readiness and governance maturity, it becomes Graduated
Key point: Maturity level does NOT guarantee the tool is the best choice — it indicates community trust and adoption.
Key Graduated Projects to Know
These are the projects most likely to appear on the KCNA exam:
Container Runtime & Orchestration
| Project | What It Does | Why It Matters |
|---|---|---|
| Kubernetes | Container orchestration platform | The core technology of the entire exam |
| containerd | Container runtime | Default runtime for Kubernetes |
| CRI-O | Container runtime for Kubernetes | Alternative OCI-compliant runtime |
Networking & Service Mesh
| Project | What It Does | Why It Matters |
|---|---|---|
| Envoy | L7 proxy and communication bus | Powers many service mesh solutions |
| CoreDNS | DNS server for Kubernetes | Default DNS in K8s clusters |
| Cilium | eBPF-based networking, security, observability | CNI plugin with advanced features |
Observability
| Project | What It Does | Why It Matters |
|---|---|---|
| Prometheus | Metrics collection and alerting | De facto standard for K8s monitoring |
| Jaeger | Distributed tracing | Tracing service-to-service calls |
| Fluentd | Log collection and forwarding | Unifying logging layer |
| OpenTelemetry | Observability framework | Merges traces, metrics, and logs into one SDK |
Application Delivery
| Project | What It Does | Why It Matters |
|---|---|---|
| Helm | Package manager for Kubernetes | Standard way to install and manage apps |
| Argo | CI/CD and GitOps toolkit | Includes ArgoCD, Argo Workflows, Argo Rollouts |
| Flux | GitOps continuous delivery | Alternative to ArgoCD |
Security
| Project | What It Does | Why It Matters |
|---|---|---|
| Falco | Runtime security and threat detection | Runtime anomaly detection |
| Open Policy Agent (OPA) | Policy engine | Admission control and policy enforcement |
The CNCF Trail Map
The CNCF Trail Map is a recommended guide for adopting cloud-native technologies. It suggests this order:
| Step | Technology | What You Do |
|---|---|---|
| 1 | Containerization | Package apps in containers (Docker, containerd) |
| 2 | CI/CD | Automate build, test, and deploy pipelines |
| 3 | Orchestration | Deploy and manage containers with Kubernetes |
| 4 | Observability & Analysis | Add monitoring, logging, and tracing |
| 5 | Service Mesh | Manage service-to-service communication |
| 6 | Networking & Policy | Implement CNI, network policies, and security |
| 7 | Distributed Databases | Handle stateful workloads |
| 8 | Messaging & Streaming | Add event-driven architecture |
| 9 | Container Registry & Runtime | Manage images and runtimes securely |
| 10 | Software Distribution | Distribute software securely (Notary, TUF) |
Landscape Categories Most Relevant to KCNA
Focus your study on these landscape categories:
| # | Category | Exam Domain | Example Tools |
|---|---|---|---|
| 1 | App Definition & Build | Application Delivery | Helm, Kustomize, Backstage |
| 2 | Continuous Integration & Delivery | Application Delivery | ArgoCD, Flux, Tekton |
| 3 | Scheduling & Orchestration | Kubernetes Fundamentals | Kubernetes |
| 4 | Container Runtime | Container Orchestration | containerd, CRI-O |
| 5 | Cloud Native Network | Container Orchestration | Cilium, Calico, CoreDNS |
| 6 | Observability | Observability | Prometheus, Jaeger, OpenTelemetry |
| 7 | Service Mesh | Container Orchestration | Istio, Linkerd, Envoy |
| 8 | Security & Compliance | Cloud Native Architecture | Falco, OPA, Trivy |
Key Takeaways for the Exam
- The CNCF Landscape organizes hundreds of cloud-native projects into categories
- Projects go through three maturity levels: Sandbox → Incubating → Graduated
- Kubernetes, Prometheus, Envoy, containerd, Helm are among the most important graduated projects
- The Trail Map provides a recommended adoption sequence for cloud-native technologies
- You don’t need to memorize every tool — focus on graduated projects and understand what category each tool belongs to
What’s Next?
Now that you understand the ecosystem, let’s make sure you’re prepared to study effectively.
