BeaverDeck logo
BeaverDeck

Home / BeaverDeck / Docs / Insights Guide / Workload Insights / Overrequested Pod

Overrequested Pod

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

When It Reports A Finding

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.

Why This Is A Problem

Persistently oversized requests reserve capacity that other workloads cannot use, inflate node requirements, and reduce bin-packing efficiency.

Recommended Response

  1. Use longer-term metrics to confirm the pod is consistently below its request across normal and peak periods.
  2. Review startup behavior, scheduled jobs, traffic cycles, and required failover headroom.
  3. Reduce requests gradually or use a right-sizing process, then watch latency, throttling, restarts, and evictions.

Scope And Limitations

The finding uses one current sample after a minimum age. Bursty, low-latency, failover, or rarely active workloads may intentionally keep substantial headroom.

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.