Kubernetes for DevOps Engineers
Kubernetes is an orchestration system that runs and manages containers across a cluster of machines. You describe desired state with objects such as Pods, Deployments, Services, ConfigMaps and Ingress, and controllers keep reality matching it. Operating it also involves packaging with Helm, resource limits, RBAC, network policies and upgrades.
Stage: Containers and Orchestration · Part of the DevOps Engineer roadmap · Last reviewed 19 November 2026
What to learn in Kubernetes
- Write a Deployment and Service manifest and apply it with kubectl
- Explain how Pods, ReplicaSets and Deployments relate
- Use ConfigMaps and Secrets to configure workloads
- Set resource requests, limits and readiness probes
- Package an application as a Helm chart
- Apply RBAC and network policies to restrict access
Kubernetes interview questions
What is the difference between a Deployment and a StatefulSet?
A Deployment manages interchangeable stateless Pods with rolling updates. A StatefulSet gives each Pod a stable identity, ordered startup and its own persistent volume, so it suits databases and systems where each replica is distinct.
What do readiness and liveness probes do?
A readiness probe tells Kubernetes when a Pod can receive traffic, so Services skip it until ready. A liveness probe detects a stuck container and restarts it. Misconfigured liveness probes can cause needless restart loops.
Where Kubernetes fits in the DevOps Engineer roadmap
Kubernetes belongs to the Containers and Orchestration stage (intermediate level), which takes about 2 hours. Package and run workloads.
Other units in this stage
Back to the full DevOps Engineer roadmap