Why Kubernetes?
Why we orchestrate containers: declarative desired state, scheduling, self-healing, scaling, rolling updates and services.
Transcript
Running one container is easy. Running hundreds of them across many machines is not.
Kubernetes is a container orchestrator: you declare what you want, and it makes it happen.
It schedules containers onto nodes with free capacity, so you never pick machines by hand.
If a container, or a whole node, dies, Kubernetes heals itself: it starts replacements elsewhere.
Need more capacity? Change the replica count, or let it autoscale, and Kubernetes adds or removes pods.
Updates are rolling: new pods replace old ones gradually, with no downtime.
A service gives pods one stable address, and load balances traffic between them.
Declare. Schedule. Heal.
More in this series
1:171Why Docker?
Images, containers, layers, and why containers are lighter than virtual machines.
2:212Why container runtimes?
Docker is one way to run containers, not the only container runtime: the OCI standards, high-level (containerd, CRI-O) vs low-level (runc) runtimes, Podman, and which runtime Kubernetes uses by default.