Back to Challenges
IntermediateScheduling & AffinityFix
Tainted Out
The pod can't schedule. Something about the nodes is blocking it. Events mention taints but the meaning is unclear.
20 min
Initial Situation
A critical application pod stays Pending indefinitely. You check node resources — plenty of CPU and memory available. Other system pods are running fine on the same node. kubectl describe pod reveals an event related to node constraints.
Your Mission0/3
Loading validation status...
Start this challenge in your local Kubernetes cluster:
$ kubeasy challenge start tainted-out