18 interactive lessons. Free to start. No signup.
Every application you deploy lives inside a Pod — the smallest deployable unit. Think of them as stones in a zen garden. Each one is self-contained, purposeful, and part of a larger pattern.
A Deployment tells Kubernetes how many pods to run and keeps them healthy. Need more capacity? Pods multiply. One fails? A new one takes its place. The garden tends itself.
Pods are ephemeral — they come and go. A Service provides a stable path to reach them, like a garden path that always leads somewhere, no matter which stones have shifted.
Ingress is the gateway to your cluster — it routes external traffic to the right service. Like the entrance to a garden, it decides which path each visitor takes.
Most of us don't need to master every API object or write custom operators. We just need enough understanding to have an intuition for how our applications behave in production.
That intuition — mechanical sympathy — is what makes you a better engineer and architect. It's the difference between copying YAML and understanding what your infrastructure is doing.
Build intuition
Interactive simulations, not memorization
First principles
Start from why, not from YAML
At your pace
No deadlines, no pressure
18 lessons. Zero fluff. From first principles to a running application.
No credit card. No signup wall. Just you and Kubernetes.
BeginFor teams
Hands-on Kubernetes consulting — architecture reviews, migration planning, and production readiness.
Get in touch