OneLinersCommand workbench
Verified diagnostic signature

The scheduler cannot place the Pod on an eligible node.

Match output from kubernetes, understand the likely cause, then continue with sourced, read-only checks.

Confidence
high
Platforms
linux · macos · windows
Verified
2026-07-24
Recognized output

Signature matched locally

didn't match Pod's node affinity

OneLiners matches this pattern in your browser. Your pasted output is not stored or indexed.

Likely causes

What usually produces this signal

  1. Resource shortage
  2. Affinity mismatch
  3. Taint without toleration
  4. Volume or topology constraint
Safe next checks

Collect evidence before changing the system

01

Show recent Kubernetes warning events in chronological order

kubectl get events -A --field-selector type=Warning --sort-by=.lastTimestamp -o custom-columns='TIME:.lastTimestamp,NAMESPACE:.metadata.namespace,REASON:.reason,OBJECT:.involvedObject.name,MESSAGE:.message'

The output matches the expected target and exits without an error.

02

Rank Kubernetes pods by memory consumption

kubectl top pods -A --no-headers | sort -k4 -hr | head -<count>

The output matches the expected target and exits without an error.