Skip to content

Kubernetes Certifications

11 modules are currently being reworked. Watch this section over the next few days.

The Kubestronaut Path — All 5 certifications required for Kubestronaut status, CNCF’s recognition for passing KCNA, KCSA, CKAD, CKA, and CKS.


KUBESTRONAUT PATH
════════════════════════════════════════════════════════
ENTRY LEVEL (multiple choice, 90 min)
┌──────────────────────────────────────────────────────┐
│ KCNA Kubernetes & Cloud Native Associate │
│ └── Conceptual understanding of K8s & CNCF │
│ │
│ KCSA Kubernetes & Cloud Native Security Associate │
│ └── Security concepts and threat modeling │
└──────────────────────────────────────────────────────┘
PRACTITIONER LEVEL (hands-on lab, 2 hours)
┌──────────────────────────────────────────────────────┐
│ CKAD Certified Kubernetes Application Developer │
│ └── Build and deploy applications │
│ │
│ CKA Certified Kubernetes Administrator │
│ └── Install, configure, manage clusters │
│ │
│ CKS Certified Kubernetes Security Specialist │
│ └── Secure clusters end-to-end (requires CKA)│
└──────────────────────────────────────────────────────┘
════════════════════════════════════════════════════════

Start with the job shape, not the alphabetical list. KCNA is useful for cloud-native context, but it is optional for learners who already need hands-on cluster work.

The operator wants production cluster administration: scheduling, networking, storage, upgrades, troubleshooting, and incident response. This is the strongest default route for SRE, infrastructure, and platform-adjacent learners who need to run clusters under pressure.

Default route: KCNA (optional) → CKA → CKS

Concrete routes:

  • Beginner -> operator: Prerequisites -> KCNA -> CKA -> CKS
  • Linux / ops -> admin: Linux -> CKA -> CKS

When to come back: after CKA or CKS, add specialist tracks such as CGOA, CCA, ICA, KCA, CAPA, OTCA, PCA, CNPA, CNPE, or FinOps when they match the platform you operate.

The developer wants to build, deploy, configure, observe, and debug applications on Kubernetes. This route focuses on workloads first, then cluster administration only if your work expands into platform ownership.

Default route: KCNA (optional) → CKAD → CKA (optional)

Concrete routes:

  • Beginner -> developer: Prerequisites -> KCNA -> CKAD
  • Application developer -> platform-aware developer: CKAD -> CKA

When to come back: after CKAD, add CGOA, CAPA, CBA, OTCA, PCA, CNPA, or CNPE when your work moves toward delivery platforms, observability, developer portals, or platform engineering.

The security specialist wants to harden clusters, workloads, supply chains, runtime behavior, and policy controls. CKS is the centerpiece, but it requires CKA first — CKS is not security-flavored Kubernetes; it assumes you can already administer clusters under time pressure. KCSA is optional conceptual prep that fits before CKA, not after CKS.

Default route: KCSA (optional) → CKA → CKS

Concrete routes:

  • Hands-on first: CKA -> CKS
  • Concepts first: KCSA -> CKA -> CKS

When to come back: after CKS, add CCA, KCA, CGOA, ICA, OTCA, PCA, CNPA, CNPE, or FinOps when your security work touches networking, policy, GitOps, service mesh, observability, platforms, or cost governance.

  • Kubernetes -> platform: KCNA or CKA -> CNPA -> CNPE
  • GitOps / platform specialist: KCNA or CKA -> CGOA / CNPA / CNPE
  • Observability specialist: CKAD or CKA -> PCA / OTCA
  • Networking specialist: CKA -> CCA / ICA

Specialist certifications are not a better first move than learning the core Kubernetes path. They make the most sense after you already understand how clusters, workloads, and operations fit together.


CertNameTypeModulesCurriculum
KCNAKubernetes & Cloud Native AssociateMultiple choice28Details
KCSAKubernetes & Cloud Native Security AssociateMultiple choice26Details
CKADCertified Kubernetes Application DeveloperHands-on lab30Details
CKACertified Kubernetes AdministratorHands-on lab47Details
CKSCertified Kubernetes Security SpecialistHands-on lab30Details
Total161

  • you want external certification goals and exam-shaped structure
  • you already finished Prerequisites or equivalent hands-on fundamentals
  • you want the shortest route into employable Kubernetes administration or application delivery skills
  • you are still uncomfortable with the terminal, SSH, files, and packages
  • you have never deployed basic workloads to a cluster
  • you are looking for theory-first platform engineering rather than certification prep

If that is your situation, start with Prerequisites first.

Beyond Kubestronaut, CNCF offers tool-specific certifications. KubeDojo maps existing modules as learning paths for each:

CertNameLearning Path
PCAPrometheus Certified AssociatePrometheus, PromQL, alerting
ICAIstio Certified AssociateService mesh, traffic management
CCACilium Certified AssociateeBPF networking, policies
CGOACertified GitOps AssociateArgoCD, Flux, GitOps principles
CBACertified Backstage AssociateIDPs, developer portals
OTCAOpenTelemetry Certified AssociateObservability, tracing
KCAKyverno Certified AssociatePolicy as code
CAPACertified Argo Project AssociateArgo Workflows, Rollouts
CNPECloud Native Platform EngineerCross-track learning path
CNPACloud Native Platform AssociatePlatform fundamentals
FinOpsFinOps PractitionerCloud cost optimization

These are best treated as specialization tracks, not replacements for a first Kubernetes foundation. For most learners:

  • KCNA, CKA, or CKAD should come first
  • specialist certs and platform certs make more sense once you know whether your work is admin, developer, security, GitOps, or platform focused
SectionModulesDescription
Extending K8s8Controllers, operators, webhooks, API aggregation, CRDs

All exams share these characteristics:

  • PSI Bridge proctoring — Strict environment, webcam required
  • kubernetes.io allowed — Official docs are your friend
  • Time pressure — Speed matters as much as knowledge

Typical pacing:

  • KCNA / KCSA: 4-8 weeks if you are already in the curriculum about 5-8 h/week
  • CKAD / CKA: 2-4 months at about 8-10 h/week
  • CKS after CKA: usually another 4-8 weeks
  • full Kubestronaut path: commonly 3-6 months for already-technical learners at roughly 10 h/week

For hands-on exams (CKAD, CKA, CKS):

  • Practice with kubectl until it’s muscle memory
  • Master vim/nano for YAML editing
  • Use kubectl explain and --dry-run=client -o yaml
  • killer.sh included with exam purchase — use it
  • go to Cloud if you want provider-specific production Kubernetes
  • go to Platform Engineering if you want systems thinking, SRE, GitOps, and platform design beyond the exams
  • go to On-Premises if your goal is private infrastructure and you already have Linux depth

Choose Your Next Track After Core Kubernetes

Section titled “Choose Your Next Track After Core Kubernetes”
If Kubernetes leads you toward…Next trackWhy
managed production clusters on AWS, GCP, or AzureCloudprovider-specific networking, identity, and managed-control-plane patterns live there
SRE, GitOps, delivery automation, and internal platformsPlatform Engineeringthat is the systems-and-organization layer above the exams
private clusters, bare metal, and datacenter operationsOn-Premisesthose assumptions diverge sharply from managed-cloud Kubernetes
ML workloads, serving, and AI infrastructureAI/ML Engineeringthe Kubernetes track is a prerequisite there, not the full workflow
  • assuming certification completion automatically means platform-engineering readiness
  • jumping into on-prem operations without enough Linux depth
  • treating specialist certifications as a substitute for choosing a real next operating context

We track official CNCF curricula: