A bank runs 200 microservices on 80 servers. On Tuesday morning, one of the servers dies. Two of the services that were running on it go offline. Pagers go off across three teams.
The operations team logs in. They find a healthy server with spare capacity. They install Docker, copy the container images, copy the config, fight with the network, start the services, update the load balancer. Forty minutes later the site is back up.
By Wednesday lunchtime, the same thing has happened to a different server. The team is tired.
Kubernetes makes the operations team unnecessary for this story. The bank declares "I want three copies of each service running, somewhere in the cluster." When a server dies, Kubernetes notices, finds spare capacity, restarts the lost services, updates the network — in seconds — while the team is still asleep.