Back to Practice
Lab

Incident: Nothing Will Schedule

The analytics rollout is stuck: every Pod is Pending and none will land on a node. Read the scheduler's own explanation and clear the blocker.

Your mission

Ticket: the analytics Deployment has been "deploying" for ten minutes. Every Pod is Pending and none has landed on a node.

Pending means the scheduler looked at the Pod and couldn't place it — this is not an image or a crash problem, it's a placement problem. And the scheduler is helpful: it records exactly why on the Pod.

kubectl get pods -n default
kubectl describe pod -n default <pod>   # read the Events — the scheduler explains itself

Restore the rollout so analytics actually runs.

Useful aliases

In your terminal, k is aliased to kubectl and completion is configured. The jumpbox also has k9s, jq and yq installed.

Skills you'll put into practice

troubleshootingincidentschedulingcka

Make it your own.

Use this topic as a starting point for a fresh custom scenario.

Create a variation