Q: You have a DaemonSet but some nodes aren't getting a pod. Why?
Common reasons:
Want to master this scenario in a live sandbox? KodeKloud's CKA & CKAD Hands-On Certification Track covers this exact problem with hands-on terminal drills.
🛠️ Production Runbook & Step-by-Step Resolution
Direct Answer: "When troubleshooting Kubernetes, I always follow a structured layered model: Pod status -> Events -> Logs -> Network. When addressing this question, I walk the interviewer through our production incident runbook: isolating the blast radius, checking diagnostic logs and metrics, and applying a safe fix."
Initial Diagnostics & Root Cause Analysis
Common reasons:
- Node selector or affinity mismatch — DaemonSet has a
nodeSelectoror affinity rule that doesn't match those nodes. - Node has a taint — the DaemonSet pods don't have a matching toleration. Add the toleration to the DaemonSet spec.
- Node is cordoned —
kubectl cordonprevents any new pod scheduling.
Remediation & Permanent Safeguards
Check: kubectl describe daemonset — look at the Selector and Tolerations. Compare with kubectl describe node .
- Node selector or affinity mismatch — DaemonSet has a nodeSelector or affinity rule that doesn't m...
- Node has a taint — the DaemonSet pods don't have a matching toleration. Add the toleration to the...
- Node is cordoned — kubectl cordon prevents any new pod scheduling.
Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:
- Over-granting cluster-admin permissions to pod ServiceAccounts instead of scoping namespace Roles when configuring DaemonSet nodes getting Over-granting cluster-wide permissions violates least-privilege principles and allows compromised pods to escalate privileges across namespaces.
-
Referencing mutable latest container tags across production Kubernetes Deployment specs when configuring DaemonSet nodes getting
Deployments referencing
:latestrisk inconsistent versions across replica pods and break deterministic rollback capabilities. - Omitting pod readiness probes, causing traffic to hit uninitialized application containers when configuring DaemonSet nodes getting Readiness probes gate traffic delivery; missing probes cause Kubernetes to route user requests to pods before dependencies or caches are loaded.
- Executing diagnostic triage without analyzing chronological cluster events and describe outputs when configuring DaemonSet nodes getting Cluster events provide sequential timestamps of scheduler decisions, probe failures, and image pull timeouts essential for rapid root-cause isolation.