Kubernetes / Deployments, Scheduling & Batch Workloads
Find why a DaemonSet does not run on an expected node
A DaemonSet's desired count depends on node eligibility and policy rather than the cluster's raw node count.
Environment and inputs: Kubernetes · kubectl with supported client/server versions and delegated RBAC. Examples use namespace app unless noted. Check context, namespace, APIs and provider support first.
Start with this check
Confirm the environment and replace sample objects, namespaces, images, paths and hosts with approved targets. Share only relevant, sanitized output. Follow the workload owner’s process for changes.
kubectl -n monitoring describe daemonset agentRead the result
The controller summary and events reveal scheduling context. Node selectors, affinity, taints and platform support can exclude nodes intentionally.
Resolve and verify
Compare the missing node's labels and taints with the approved agent design. Correct the specific placement mismatch and verify the agent's actual function.
Before changing production
Do not add universal tolerations or privileged access just to make a monitoring count equal all nodes.