Payments service, mission 2 of 4
Not dead, just slow
advanced, about 12 minutes, in the Kubernetes Simulator
Opens once you pass Migrate, then release.
The briefing
From Priya Raman, senior backend developer at Larchwood (a fictional company)
The 2.0 rollout has been stuck since yesterday. Its pods restart forever — Killing … failed liveness probe in the events — and 1.0 is still carrying all traffic.
2.0 isn't broken: it loads its fraud model at startup and takes about 50 seconds to listen. I don't want to lose the liveness probe; it caught a real deadlock last month. payments.yaml is the manifest.
What you'll do
- payments: 2 ready replicas on 2.0
- Still guarded by a liveness probe
- A startup probe gives it time to start
- Bonus star: Keep the liveness probe exactly as it was
The mission checks the cluster, not your keystrokes: any fix that works, passes.
Concepts
Startup probes
A probe that runs first and alone. Until it succeeds, liveness and readiness probes don't run, so a slow starter isn't killed for being slow. It gets
Read the Kubernetes docsfailureThreshold × periodSecondsto start; once it passes, the liveness probe takes over at its usual, tighter settings.
More Payments service missions
- 1. Migrate, then release
- 2. Not dead, just slow
- 3. No shell
- 4. Charged twice