The CKA exam, the Certified Kubernetes Administrator exam from the CNCF, is a two-hour online test taken directly at the terminal, where you fix real problems in running Kubernetes clusters instead of answering multiple-choice questions. According to the CNCF page, as of September 2026, it costs 445 US dollars, including one free retake, and tests five domains from cluster installation to troubleshooting. Pass it, and according to the exam provider Linux Foundation Training, as of September 2026, you hold a certificate valid for two years that shows you can not just explain a cluster, but actually run one.
I am a CNCF Kubestronaut, having passed all five Kubernetes certifications including the CKA, and I run production Kubernetes clusters on Hetzner. I cover how the Kubestronaut program fits together in Kubestronaut: What Is It?. You can find all my Kubernetes articles on the Kubernetes page.
CKA exam format: two hours, a real terminal, no multiple choice
The CKA is a performance-based test: you get several tasks spread across several prepared Kubernetes clusters, and you solve them from the command line instead of picking an answer. Each task comes with a specific context you switch into first. A proctor watches the session online, screen and camera included. The time limit is two hours for all tasks combined. The CNCF keeps moving the exam to newer Kubernetes versions; which one currently applies is stated in the curriculum repository, and that is where to check before you register.
During the exam you are allowed to open the official Kubernetes documentation and a handful of other CNCF-approved pages in a separate browser tab, everything else is locked down. That shifts what preparation should look like: it matters less that you have memorized every field name, and more that you can find the right doc page and move fast enough with kubectl to finish in time. If you mostly work through a graphical interface day to day, that gap is exactly what to train before the exam.
The five domains of the CKA curriculum
The CNCF curriculum, published in the curriculum repository on GitHub, splits the CKA exam into five domains with clearly different weights. Troubleshooting carries by far the largest weight, a clear signal of how the CNCF sees the administrator role: fewer objects created from scratch, more broken clusters fixed.
| Domain |
Weight |
| Cluster Architecture, Installation & Configuration |
25% |
| Workloads & Scheduling |
15% |
| Services & Networking |
20% |
| Storage |
10% |
| Troubleshooting |
30% |
These weights change with every curriculum version, and the file names in the repository track the Kubernetes version being tested. When preparing, always check the newest file in the repository rather than relying on older course material, Kubernetes objects and fields shift between versions.
Preparation: what actually matters
Just reading gets you little on a hands-on test. The preparation that worked for me had three parts: first, use the official Kubernetes documentation often enough that you find the right page in seconds, because that exact skill is what the exam demands. Second, solve every practice task against a timer, not just until the answer is correct, but until it is fast enough. Third, internalize the standard troubleshooting tools, kubectl describe, kubectl logs, kubectl get events, until reaching for them is automatic.
One thing most prep lists skip: setting up kubectl shortcuts and autocompletion genuinely saves minutes during the exam, and minutes are tight when several tasks share a two-hour window. It also helps to get comfortable with vim or whichever editor the exam environment offers, rather than fighting its keybindings for the first time during the actual test.
Practice setup: build your own cluster to train on
The most useful practice happens on a cluster that feels like a real exam situation: several nodes, real failures, no clicking through a UI. A local multi-node cluster with kind or k3d is entirely enough for this and costs nothing. What matters is deliberately breaking things, a wrong selector on a service or a missing secret, for example, instead of only typing out manifests that already work. Those broken states are exactly what the troubleshooting tasks simulate, and troubleshooting alone accounts for 30 percent of the score.
kubectl get pods --all-namespaces --field-selector=status.phase!=Running
kubectl describe pod <name> -n <namespace>
kubectl logs <name> -n <namespace> --previous
kubectl get events -n <namespace> --sort-by=.lastTimestamp
In practice, these four commands in sequence cover most failure patterns I run into: find pods that are not running, spot the cause in the event history or the logs, decide whether a restart or a config change is needed. Once that sequence is automatic, you stop losing exam time thinking about what to check next.
Tips from taking the exam
The biggest trap in a time-boxed exam is getting stuck on a single task. Every task carries a point value, and a hard task worth few points costs the same time as an easy one worth many. It pays to skim all tasks first, rough out an order and a time budget, and skip a task that is not moving fast enough, with the option to return to it later.
Just as important: check the current context before you start typing. The exam switches between several clusters, and running kubectl config current-context at the start of every task keeps you from entering an otherwise correct answer into the wrong cluster, a mistake that has cost me time myself. And apply every change to the cluster right away instead of leaving it sitting in an editor, because what gets graded in the end is the state of the cluster. A dropped connection mid-exam is then unpleasant, but not a disaster.
How it differs from CKAD and CKS
The CNCF offers two more Kubernetes certifications alongside the CKA, and both differ clearly in audience and content. The CKAD, Certified Kubernetes Application Developer, targets developers who build and deploy applications for Kubernetes, with a focus on application design, deployment, configuration and observability rather than cluster operations. The CKS, Certified Kubernetes Security Specialist, requires a passed CKA first and goes deep on security: cluster and system hardening, minimizing microservice vulnerabilities, supply chain security, and monitoring plus runtime security.
| Certification |
Audience |
Focus |
| CKA |
Administrators |
Install, configure, run and fix a cluster |
| CKAD |
Developers |
Design and deploy applications for Kubernetes |
| CKS |
Administrators with a passed CKA |
Security in the cluster and the supply chain |
If you run clusters for a living, the CKA is usually the right place to start, since it lays the broadest foundation. An overview of all Kubernetes certifications and how they connect is in Kubernetes Certifications: CKA, CKAD & More.
Frequently asked questions
How long does the CKA exam take?
Two hours for all tasks combined. The clock runs across the whole exam, not per task, which is why a rough time budget per task before you start helps you avoid getting stuck on any single one.
What is the difference between CKAD and CKA?
The CKAD tests the developer perspective, designing, deploying and configuring applications, while the CKA tests the administrator perspective, installing, securing and fixing a cluster. Both share basic knowledge of pods and workloads, but the focus differs substantially.
Do I need prior experience for the CKA exam?
Formally, the CNCF sets no prerequisite. In practice, though, you need solid command-line skills, a basic grasp of Linux, and hands-on experience with Kubernetes objects, reading the documentation alone will not get you through in time.
How long is the CKA valid?
Two years from the day you pass. For certifications earned before 1 April 2024, the Linux Foundation states three years (certification FAQ). After that you have to sit the exam again; there is no renewal through continuing education.
How many times can I retake the CKA exam?
The price includes one free retake if your first attempt does not pass. After that, you can book the exam again for a fee.
Where to go from here
Requests, limits, storage concepts and the failure patterns the CKA exam tests are covered with full examples in my Kubernetes Practical Guide (Rheinwerk Computing). Find everything about the book on my Kubernetes page.
My suggestion for the next step: spin up a small practice cluster with kind or k3d, download the current curriculum PDF from the CNCF curriculum repository, and work through the domains one by one, against a timer. A broader learning roadmap toward Kubestronaut, including which order the five certifications are worth taking in, is in Learn Kubernetes: Kubestronaut Roadmap.
