Nowadays, many of you (developers, sysadmins, ...) use Kubernetes in one way or another. You know what a container is and that you can trust Kubernetes to reliably deploy it in production.

But beyond that, have you ever wondered "how" Kubernetes actually works?

Between the moment you run a `kubectl apply` (or a `helm install`) on your PC and the moment the application becomes accessible, what has happened?

When a node fails, what ensures that the application is restarted on another node without the need to wake up the on-call human?

How is it possible to access any container in our cluster without requiring a seasoned network administrator for every new deployment?

I invite you to dissect together all the internal components of Kubernetes to discover that "no, Kubernetes is not magical."