Skip to content

Kubernetes roadmap

Run, secure and troubleshoot containerised applications at scale.

4 to 6 months at 8 to 10 hours a week7 stages34 topicsSome experience helps

All roadmaps

Kubernetes keeps containerised applications running: it schedules them, restarts them, scales them and rolls out new versions. This path covers the workloads, networking, storage and cluster administration skills that day-to-day work and the CNCF exams both rely on.

Where you will end up

You can deploy and expose an application, configure it safely, diagnose a broken cluster methodically, and stand up and upgrade a cluster yourself. That is the skill set behind the Certified Kubernetes Administrator exam and platform engineering interviews.

Before you start

  • Comfortable with the Linux command line
  • Can build and run containers (see the Docker roadmap)
  • Basic networking: IP addresses, ports and DNS

Roles it leads to

  • DevOps Engineer
  • Platform Engineer
  • Site Reliability Engineer
  • Cloud Engineer
  1. 1

    Core concepts and workloads

    3 to 4 weeks0 of 6 done

    Deploy an application declaratively and understand how Kubernetes keeps it running.

    Prove it

    Deploy, update and roll back

    Deploy an app with three replicas, perform a rolling update to a new image, deliberately break the release, and roll back. Capture the commands you used.

  2. 2

    Services and networking

    3 weeks0 of 4 done

    Make workloads reachable and control which pods may talk to each other.

    Prove it

    Expose and isolate

    Publish a web app through an ingress or gateway, then add network policies so only the front end can reach the database. Prove the blocked path fails.

  3. 3

    Configuration and storage

    2 to 3 weeks0 of 4 done

    Separate configuration from images and keep state safe when pods move.

    Prove it

    Stateful app that survives

    Run a database with a persistent volume, store data, delete the pod, and confirm the replacement pod sees the same data. Configure the app only via ConfigMap and Secret.

  4. 4

    Scheduling and scaling

    2 weeks0 of 4 done

    Control where workloads run and make them scale and run on a schedule.

    Prove it

    Scale under load

    Configure autoscaling for a deployment, generate load, watch replicas grow and shrink, and explain every number you saw.

  5. 5

    Cluster administration

    4 weeks0 of 5 done

    Build, secure, back up and upgrade a cluster yourself.

    Prove it

    Build, upgrade, restore

    Create a multi-node cluster with kubeadm, upgrade it one minor version, take an etcd snapshot, and restore from it. Document every step and the mistakes you made.

  6. 6

    Troubleshooting

    3 weeks0 of 5 done

    Find the cause of a broken workload, node or cluster quickly and methodically.

    Prove it

    Fix five broken clusters

    Have a friend, or a script you wrote, break a cluster in five different ways. Diagnose and repair each within a time limit and write a short postmortem for each.

  7. 7

    Production practice

    3 to 4 weeks0 of 4 done

    Package, secure and deliver applications to Kubernetes the way teams do it.

    Prove it

    A real delivery path

    Package your app with Helm, enforce the restricted pod security profile on its namespace, and have a GitOps tool deploy it from a repository.

Certifications that fit

Optional, and never a substitute for projects. Exam details change, so confirm on the official page before you book.

The honest part

Kubernetes is learned on a real cluster, not by reading. Build a small cluster at home or in the cloud, break it deliberately and fix it. The performance-based exams reward speed with kubectl, so practise in a terminal every day with the official documentation open, and read the current exam rules for exactly what is permitted.

Checked against

Written by CloudIskole and reviewed against the official sources below. Last verified November 2026. Spotted something out of date? Tell us and we will fix it.

These roadmaps are our own work. For another community view of learning paths, see roadmap.sh, which inspired the idea of a visual guide.