Home / BeaverDeck / Docs / Insights Guide / Node Insights / Node Conditions

Node Conditions

BeaverDeck uses this check to identify a specific node 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	`node-condition`
Insights section	Node Insights
Alert severity	Critical

When It Reports A Finding

A Node has Ready set to anything other than True, or reports active MemoryPressure, DiskPressure, PIDPressure, or NetworkUnavailable.

Why This Is A Problem

An unhealthy node can stop accepting workloads, evict pods, lose network reachability, or fail existing workloads. Pressure conditions often precede broader availability incidents.

Recommended Response

Open the Node and review the condition reason and message shown by BeaverDeck.
Inspect kubelet, container runtime, disk, memory, PID, and CNI health according to the reported condition.
If workloads are at risk, cordon and drain the node using the cluster's maintenance procedure, then repair or replace it.
Uncordon only after the Node is Ready and pressure conditions have cleared.

Scope And Limitations

The check reflects Kubernetes Node conditions. It does not diagnose the underlying host failure or replace infrastructure monitoring.

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