Kubernetes Advanced About 30 min +260 XP

Ledger Rollout Leaves Every Pod Crashing

Both pods from the new ledger revision crash on startup, leaving one old pod to carry every ledger write.

Briefing

ledger 1.7.0 started rolling out five minutes ago and both of its new pods have crashed on every start since.

The rollout has stalled with a single pod from the previous release still Running, so ledger is up, but on half its capacity and with no redundancy in the payment settlement path.

Maya has authorized putting the previous build back while the release team works out what 1.7.0 broke.

Dev reads the crash message as the database refusing the new pods and wants to bounce the connection pooler first.

The fix is yours to find: hints, the recovery checks and the debrief unlock inside the incident.

How it plays

  1. 01

    Get paged

    The alert fires and the clock starts. Read the page and the briefing.

  2. 02

    Investigate

    Work in a simulated shell with realistic output: logs, configs, services.

  3. 03

    Fix it

    Change the system the way you would in production. Hints are there if you get stuck.

  4. 04

    Prove it

    Automated checks verify the recovery, then the debrief explains what happened.

Your pager is ready.

Free, instant, and it works on your phone. No signup: start as a guest and save your progress later.