Kubernetes
A machine for keeping promises - and reading why it could not.
- 1Desired state and self-healingYou don't tell Kubernetes what to do. You tell it what you want, and it keeps checking. Make a promise, break it on purpose, and watch it get kept.Runs in your browserOn your machine14 min+35 XP
- 2Why won't it schedule?A pod stuck in Pending has a reason, and it's never printed where you're looking. Find it, read it, and fix the request rather than the cluster.Runs in your browserOn your machine14 min+35 XP
- 3Why did it restart?Two pods crash forever, both with exit code 137, and they need opposite fixes. Learn which two fields tell them apart before you reach for more memory.Runs in your browserOn your machine18 min+45 XP
- 4The pods that were never bornThe deployment wants six and has three. Nothing is crashing, nothing is Pending, and there's no broken pod to look at. Find where the refusal is written down.Runs in your browserOn your machine16 min+40 XP
- 5A typo is not an outageA rolling update only retires an old pod once a new one is Ready. Ship a broken image tag, watch the old version keep serving, and finish the rollout properly.Runs in your browserOn your machine16 min+40 XP
Next track: Platform & CNCF →