Kubernetes Intermediate About 30 min +220 XP

Gateway Pods Run but Receive No Traffic

Both gateway pods have been Running for ten minutes and neither has ever become Ready, so no gateway replica is eligible for traffic.

Briefing

gateway 2.3.0 went out ten minutes ago with a refactored manifest.

Both pods started straight away and neither has restarted once, yet neither has ever reported Ready, and the rollout has now blown through its progress deadline.

This is the gateway's first deploy to this cluster, so there is no older ReplicaSet to fall back on, and partner API calls are failing.

Sam thinks 2.3.0 is hanging on a new startup dependency and wants to roll back to 2.2.

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.