Kubernetes for DevOps Roadmap
A staged path through Kubernetes — from core objects and config to networking, resource management, and production operations.
0%
0 of 12 topics complete
- Done
- To do
- Optional
Tick a topic as you finish — saved in this browser only.
-
Core objects
The three primitives everything else builds on.
-
The smallest deployable unit in Kubernetes.
-
Declarative rollouts and replica management.
-
ClusterIP, NodePort, and LoadBalancer.
-
-
Config
Separate config and secrets from your container images.
-
Inject non-sensitive config into pods.
-
Base64-encoded secrets and how to handle them safely.
-
Logical isolation within a cluster.
-
-
Networking
Route external traffic into your cluster.
-
HTTP/HTTPS routing, TLS termination, and path rules.
-
-
Resources
Prevent noisy-neighbour problems and right-size your pods.
-
CPU and memory budgets and the QoS classes.
- Kubernetes resource calculator optional
Compute requests and limits interactively.
-
-
Operations
Keep apps healthy and debug when they are not.
-
liveness, readiness, and startup probes.
-
Zero-downtime deploys and safe undo.
-
CrashLoopBackOff, ImagePullBackOff, and beyond.
-
Why this order.
Kubernetes has a reputation for complexity that is only half-deserved. The object model is small — a handful of resources that compose — and most of the difficulty is that people meet those objects in the wrong order, usually starting with a Helm chart that hides all of them.
So this starts with pods and deployments in isolation, then adds Services and Ingress once there is something to route to. Config and secrets come next because they are what turns a demo into something you would deploy twice. Resource requests and limits get their own stage rather than a footnote, because they decide scheduling and eviction, and getting them wrong produces OOMKills that look like application bugs.
Production operations comes last: probes, rollouts, and the debugging loop for when a pod will not start. By then the failure modes are legible, because you know what each object was supposed to do.