BeaverDeck logo
BeaverDeck

Home / BeaverDeck / Docs / Insights Guide / Workload Insights / Pod Request Usage

Pod Request Usage

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 typepod-request-usage
Insights sectionWorkload Insights
Alert severityWarning

When It Reports A Finding

For a Running Pod with metrics available, current CPU usage or memory usage is greater than the corresponding Pod request.

Why This Is A Problem

Sustained usage above requests means the scheduler reserved less capacity than the workload consumes. This can reduce placement accuracy and increase contention or eviction risk.

Recommended Response

  1. Confirm that the sample represents sustained behavior rather than a short burst.
  2. Compare current and historical usage with requests, limits, replicas, and autoscaling targets.
  3. Raise requests, improve application efficiency, or scale horizontally according to the workload pattern.

Scope And Limitations

This is a current metrics sample. CPU usage above a request is not itself CPU throttling, and short bursts can be healthy. No result is produced when pod metrics are unavailable.

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.