https://www.youtube.com/watch?v=yqXtFKrsR6Q

Most people learn Kubernetes as a parts list. API server. Scheduler. Controller manager. Kubelet. Etcd. Kube-proxy. Once the names are memorized, the parts list never collapses into a system. You can recite the components but you can't predict the cluster's behavior.

Forget the parts list.

Kubernetes is one idea, repeated. Once you see it, every component becomes the same shape applied to a different object.

What Kubernetes is for

Docker runs a container on your laptop. One container, one machine, you watch it yourself. Production isn't that. Production is many containers across many machines. Some crash. Some hang. Some get evicted because their host ran out of memory. You want three replicas of your service running on different nodes, restarting forever, no matter what fails.

That's the bridge problem. Someone has to watch what's running, compare it to what you wanted, and fix the gap.…