Kubernetes / Deployments, Scheduling & Batch Workloads
Diagnose a DaemonSet rollout stuck on one node
An agent rollout can remain incomplete because one node cannot pull the image, satisfy resources or become ready.
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 rollout status daemonset/agent --timeout=30sRead the result
The bounded observation reports update progress without restarting agents. Node-specific Pod evidence is needed for the actual cause.
Resolve and verify
Identify the unready replacement and correlate image, node and probe events. Repair that dependency and confirm desired updated availability.
Before changing production
Do not restart every node or remove the old working agent while its replacement is unhealthy.