Hands-on Linux and Kubernetes experience
RecommendedThe Linux Foundation rates CKA an intermediate exam. Every task is done at the command line in a live cluster.

Validates practical skills in Kubernetes cluster setup, workloads and scheduling, services and networking, storage, and troubleshooting.
CKA tests whether you can build, run, secure and repair Kubernetes clusters under time pressure. Learn each domain hands-on, practise kubeadm builds, upgrades and troubleshooting until they are routine, then use the two included Killer.sh sessions to rehearse speed.
Example scenario: A node shows NotReady after a restart and new Pods stay Pending. Which components and logs would you check first?
Example scenario: A team needs read-only access to Pods in one namespace. Which RBAC objects would you create?
Example scenario: A database Pod should accept traffic only from Pods labelled app=api. How would you write the NetworkPolicy?
Official CKA curriculum · Kubernetes v1.37
Performance-based. Solve each task from a Linux terminal: connect to the named cluster, run kubectl and system commands to build or repair the setup, and leave the cluster in the state the task describes.
In the cluster named in the task, give the service account audit in namespace web read-only access to Pods in that namespace. Create a Role named pod-reader and bind it to the account.
kubectl create role pod-reader --verb=get,list,watch --resource=pods -n web, then kubectl create rolebinding pod-reader-binding --role=pod-reader --serviceaccount=web:audit -n web. The Role grants read-only Pod access and the binding assigns it to the account.
Buy the exam from the Linux Foundation, then schedule with PSI at least 24 hours ahead. You have 12 months to take the exam and your retake.
Start by checking how fast you are in a live cluster, then learn each domain by doing it.
Most candidates spend 40–100 hours. Plan for the low end if you already run clusters and only need practice on kubeadm upgrades, Helm, Gateway API and timed tasks; add time if you use Kubernetes but have not administered clusters.
Pick one course with hands-on labs, and use the Kubernetes docs as you go, since you can open them in the exam.
Practise in the docs Find manifest examples in kubernetes.io/docs while you study. Fast lookup saves more time in the exam than memorised YAML.
Your exam purchase includes two Killer.sh sessions. Use one midway and one a few days before the exam.
See all 4 CKA practice tests →The exam is online only. Prepare your room and computer before check-in.
One February 2026 passer lists the easy ways to lose points: a wrong resource or container name, the right object in the wrong namespace, or a mismatched port or selector. They finished with 40 minutes left and used it to recheck every task.
KodeKloud's instructors tell worried candidates that Killer.sh is harder than the real exam. Use it to build speed and find gaps, not to predict your score.
A 2026 candidate found the exam harder than older reports suggested, because the February 2025 revision added Helm, Kustomize, Gateway API, NetworkPolicy and CRD work. Another passer combined a course, Kubernetes the Hard Way and both Killer.sh sessions.