Kubernetes Simulator

Put nginx on the cluster, give it an address, scale it for launch day and ship v2 — then survive the 3am page.

1. 1. Your first podbeginner · ~5 min
2. 2. Pods that healbeginner · ~8 min
3. 3. Give it an addressbeginner · ~8 min
4. 4. Launch daybeginner · ~8 min
5. 5. Ship v2intermediate · ~10 min
6. 6. The 3am pageintermediate · ~12 min

Config and secrets, a crash loop, health checks, memory limits, a launch-day traffic spike and a rotated password — for a service people depend on.

1. 1. Config, not codeintermediate · ~10 min
2. 2. CrashLoopBackOffintermediate · ~10 min
3. 3. Ready when it's readyintermediate · ~10 min
4. 4. Out of memoryintermediate · ~10 min
5. 5. Launch-day trafficadvanced · ~12 min
6. 6. Rotate the passwordadvanced · ~12 min

Jobs that run to the end and stop: retries, parallel work, a nightly CronJob, runs that pile up, and a 2am failure to backfill.

1. 1. Run it onceintermediate · ~8 min
2. 2. When a job failsintermediate · ~10 min
3. 3. Many handsintermediate · ~10 min
4. 4. Every nightintermediate · ~10 min
5. 5. Pile-upadvanced · ~10 min
6. 6. The 2am failureadvanced · ~12 min

Servers with names that stay put, saves that survive a restart, a one-server canary, draining a node without emptying the arena — and a server stranded by its own disk.

1. 1. Every server has a nameadvanced · ~10 min
2. 2. Saves that surviveadvanced · ~12 min
3. 3. One server firstadvanced · ~10 min
4. 4. Don't empty the arenaadvanced · ~12 min
5. 5. Strandedadvanced · ~10 min