The report Deployment has run zero workers for ten minutes; its only pod is still waiting to be scheduled.
Stage 5 of 5 in Kubernetes Night Shift.
The nightly reports start at 10:00, and the report Deployment has not run a single worker after a resource change was applied at 09:20.
The cluster is one small node that is mostly idle.
Whoever made the change left no manifest in the workspace, only a README with the usual sizing.
Sam's first thought is a taint from this afternoon's node maintenance.
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.