Chapter 1
Why Kubernetes?
The problem it solves
Your app runs on one server. Traffic spikes. The server crashes. Your phone rings at 3 AM. That was life before container orchestration — manual, fragile, exhausting. Kubernetes (K8s for short) automates that pain away by treating your fleet of machines as one big computer that scales and heals itself.
The Old Way
Pod crashes at 3 AM
On-call gets paged
You SSH in to investigate
Manually restart the service
Back up after 30 minutes
The Kubernetes Way
Pod crashes at 3 AM
Controller detects within seconds
Scheduler places a replacement Pod
New Pod healthy in under 10 seconds
You stay asleep. Users never noticed.
Key takeaways
- Kubernetes orchestrates containers across many machines as one system
- It self-heals — failed workloads are automatically replaced
- It scales workloads up and down with demand
- You declare the desired state; K8s continuously works to reach it