BeaverDeck logo
BeaverDeck

Home / BeaverDeck / Docs / Insights Guide / Workload Insights / Resource Requests

Resource Requests

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 typemissing-requests
Insights sectionWorkload Insights
Alert severityWarning

When It Reports A Finding

An active Pod has an init or application container with no CPU request or no memory request.

Why This Is A Problem

The scheduler and capacity planning cannot represent the workload accurately. Missing requests can produce poor placement, unreliable autoscaling, and greater eviction risk under pressure.

Recommended Response

  1. Measure normal and peak usage for every listed container.
  2. Set realistic CPU and memory requests in the owning workload, preserving enough headroom for startup and bursts.
  3. Review limits and autoscaling together so requests do not conflict with the intended scaling model.

Scope And Limitations

The check verifies that requests exist, not that their values are correct. Init containers are included; terminal pods are ignored.

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.