Home / BeaverDeck / Docs / Insights Guide / Workload Insights / DaemonSet Readiness

DaemonSet Readiness

BeaverDeck uses this check to identify a specific workload condition that may need operator review.

Permissions: viewing checks requires insights: view. Opening a linked object or logs requires the corresponding resource permission, and the BeaverDeck ServiceAccount must be allowed to read the Kubernetes resources used by the check. Suppressing a finding requires insights: edit and affects all users.

Check type	`daemonset-readiness`
Insights section	Workload Insights
Alert severity	Warning

When It Reports A Finding

A DaemonSet's desired scheduled pod count is greater than its ready pod count.

Why This Is A Problem

A node-level agent that is missing from one or more target nodes can create monitoring, networking, storage, security, or operational coverage gaps.

Recommended Response

Compare desired, current, ready, available, and updated counts in the finding.
Inspect the DaemonSet rollout and the failing pods, including events and logs.
Check node selectors, affinity, taints and tolerations, image pulls, resource pressure, and update strategy.
Fix the owning DaemonSet rather than editing an individual managed pod.

Scope And Limitations

The check compares desired and ready counts. A short rollout or recently added node can produce a temporary warning.

After remediation: refresh Workload Insights and verify the underlying resource or metric. Suppress the finding only when the condition is intentional and its risk is accepted.