Kubernetes Intermediate About 30 min +220 XP

Payment Pods Stuck Before Startup

The payment pod has been stuck before startup for ten minutes, leaving the payment Deployment with zero ready replicas.

Stage 2 of 5 in Kubernetes Night Shift.

Briefing

A settings rollout for payment went out at 09:20 together with a refresh of its ConfigMap, and the new payment pod has not started since.

The image is the same one that ran yesterday, the pull succeeded, and the kubelet has been retrying for ten minutes and getting nowhere.

Payments are queuing at the gateway while customers watch a spinner.

Dev thinks the kubelet simply has not caught up with the refreshed ConfigMap yet and wants to give it a few more minutes.

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.