Home / BeaverDeck / Docs / Insights Guide / Workload Insights

Workload Insights

Scheduling, readiness, restart, memory, and CPU/memory request quality for pods and DaemonSets.

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.

Data Evaluated

Pods, pod events, DaemonSets, resource requests, and current pod metrics for the selected namespaces.

Checks

Check	When it reports	Alert severity
DaemonSet Readiness `daemonset-readiness`	A DaemonSet's desired scheduled pod count is greater than its ready pod count.	Warning
Pod Pending `pod-pending`	A Pod remains in `Pending` for at least 10 minutes.	Warning
Container Waiting `container-waiting`	An init or application container is waiting with `CrashLoopBackOff`, `ImagePullBackOff`, or `ErrImagePull`.	Warning
OOMKilled `oomkilled`	The current or previous terminated state of an init or application container reports reason `OOMKilled`.	Warning
Pod Restarts `pod-restarts`	The total restart count across init and application containers is at least 3.	Warning
Resource Requests `missing-requests`	An active Pod has an init or application container with no CPU request or no memory request.	Warning
Pod Request Usage `pod-request-usage`	For a Running Pod with metrics available, current CPU usage or memory usage is greater than the corresponding Pod request.	Warning
Overrequested Pod `pod-under-request`	A Running Pod is at least 15 minutes old and, with metrics available, CPU usage is below 20% of a request of at least 100m or memory usage is below 20% of a request of at least 128 MiB.	Warning

Open an individual check for risk context, recommended response, and limitations. Passing checks are visible when Show all checks is enabled in BeaverDeck.