Calls to the catalog Service are refused even though both catalog pods are Running and Ready.
Stage 4 of 5 in Kubernetes Night Shift.
The catalog rollout finished ten minutes ago and every pod dashboard is green: two replicas, Ready, no restarts.
Anything inside the cluster that calls the catalog by its Service name gets connection refused, and product pages are rendering with blank prices.
The Deployment and its Service were consolidated into a single stack.yaml earlier this week.
Dev suspects kube-proxy on the node.
The fix is yours to find: hints, the recovery checks and the debrief unlock inside the incident.
The alert fires and the clock starts. Read the page and the briefing.
Work in a simulated shell with realistic output: logs, configs, services.
Change the system the way you would in production. Hints are there if you get stuck.
Automated checks verify the recovery, then the debrief explains what happened.
Free, instant, and it works on your phone. No signup: start as a guest and save your progress later.