Kubernetes Simulator

advanced · ~15 min

Charged twice

Ticket from Tom Okafor, product manager

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.

Pause, history, undo

kubectl rollout pause freezes a Deployment mid-rollout: no more pods are replaced until rollout resume. rollout history lists revisions, one per template; --revision=N shows one. rollout undo --to-revision=N makes revision N's template current again — a new rollout. A paused Deployment can't be undone until it's resumed. Docs

Objectives

  • Every payments pod back on 2.0, 4 ready
  • The rollout isn't left paused
  • Bonus: Never more than two pods on 2.1

Best on a computer with a keyboard. It works on a phone, with shortcuts under the terminal.