Bird
0
0

Why might a DaemonSet pod fail to run on a node even if the node matches the nodeSelector labels?

hard📝 Conceptual Q10 of 15
Kubernetes - Scheduling
Why might a DaemonSet pod fail to run on a node even if the node matches the nodeSelector labels?
AThe node has a taint that the pod does not tolerate
BThe pod image is too large
CThe DaemonSet selector is missing
DThe pod uses hostPath volumes
Step-by-Step Solution
Solution:
  1. Step 1: Understand taints and tolerations

    Nodes can have taints that prevent pods from scheduling unless pods have matching tolerations.
  2. Step 2: Identify cause of pod not running

    If nodeSelector matches but pod does not tolerate node taints, pod will not run on that node.
  3. Final Answer:

    The node has a taint that the pod does not tolerate -> Option A
  4. Quick Check:

    Node taints block pods without tolerations [OK]
Quick Trick: Pods must tolerate node taints to run on tainted nodes [OK]
Common Mistakes:
  • Ignoring node taints when pods fail to schedule
  • Blaming pod image size for scheduling failure
  • Confusing missing selector with scheduling issues

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Kubernetes Quizzes