Payments service, mission 4 of 4
Charged twice
advanced, about 15 minutes, in the Kubernetes Simulator
Opens once you pass No shell.
The briefing
From Tom Okafor, product manager at Larchwood (a fictional company)
2.1 is going out right now. Support says the first customers are already writing in about being charged twice — it has to stop before every pod is on it.
Put payments back on 2.0, which was fine all week. The release bot is the only thing that changes payments, so whatever you do is the last word.
What you'll do
- Every payments pod back on 2.0, 4 ready
- The rollout isn't left paused
- Bonus star: Never more than two pods on 2.1
The mission checks the cluster, not your keystrokes: any fix that works, passes.
Concepts
Pause, history, undo
Read the Kubernetes docskubectl rollout pausefreezes a Deployment mid-rollout: no more pods are replaced untilrollout resume.rollout historylists revisions, one per template;--revision=Nshows one.rollout undo --to-revision=Nmakes revision N's template current again — a new rollout. A paused Deployment can't be undone until it's resumed.
Read first
More Payments service missions
- 1. Migrate, then release
- 2. Not dead, just slow
- 3. No shell
- 4. Charged twice