Certified Kubernetes Administrator (CKA)
Run, network and troubleshoot clusters from the command line, the way the hands-on exam tests it.
8 topics · about 6 hours of reading
No background needed. Work through four stages in order. Every topic says what to know first and what you'll be able to do afterwards, and every lesson starts in plain words before it goes deep.
Tell us what you're preparing for. AI picks the topics that matter and orders them, then your dashboard shows what to read each week.
Loading the planner…
Each path picks the topics that matter for one goal, in a sensible order. Choosing one sets your study plan; you pick the finish date on the dashboard. These are our suggestions, so check the official exam guide for any certification.
Run, network and troubleshoot clusters from the command line, the way the hands-on exam tests it.
8 topics · about 6 hours of reading
Networking, identity, DNS, storage, serverless and cost: the services the exam is built around.
11 topics · about 5 hours of reading
The topics most interviews probe, finishing with full mock interviews.
12 topics · about 8 hours of reading
Measure, alert, respond and recover: SLOs, incidents and the systems underneath.
11 topics · about 6 hours of reading
Build the paved road other teams deploy on: Kubernetes, GitOps, IaC, policy and a portal.
12 topics · about 6 hours of reading
How computers, Linux, Git and networks work. Everything else assumes these.
Containers, AWS, Terraform, CI/CD pipelines and web serving: the daily toolkit.
Kubernetes, EKS, GitOps, service mesh, safe releases and databases: running software at scale.
Observability, reliability, security, platforms, cost, AI workloads and interviews: what makes you senior.
Good to have; some job descriptions ask for them.
The lessons are about 25 hours of reading. With labs and tests, plan for roughly three to four times that.
At an hour a day, most people finish the foundations in a few weeks and the whole path in a few months. Going steadily beats cramming: revisit a topic's tests a week later to make it stick.
Already working in DevOps? Skim stage 1, take its tests, and spend your time where you score lowest. The dashboard shows your weak spots.