Home / BeaverDeck / Docs / Insights Guide / Node Insights

Node Insights

Node health, metrics availability, requested-resource pressure, and low requested utilization.

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

Node objects, node conditions, allocatable CPU and memory, scheduled pod requests and limits, metrics-server, and the kubelet metrics fallback.

Checks

Check	When it reports	Alert severity
Metrics Pipeline `metrics-pipeline`	The `metrics.k8s.io/v1beta1` API is unavailable. The finding is a warning when BeaverDeck can use direct kubelet `/metrics/resource` scraping, and critical when that fallback also fails.	Warning; critical if both metrics paths fail
Node Conditions `node-condition`	A Node has `Ready` set to anything other than `True`, or reports active `MemoryPressure`, `DiskPressure`, `PIDPressure`, or `NetworkUnavailable`.	Critical
Node Underutilization `node-underutilized`	On a schedulable node with known allocatable resources, combined scheduled pod CPU requests and memory requests are both below 50% of allocatable capacity.	Warning
Node Capacity `node-capacity`	The combined CPU requests, CPU limits, memory requests, or memory limits of scheduled non-terminal pods exceed the node's allocatable value for that resource.	Critical

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