BeaverDeck logo
BeaverDeck

Home / BeaverDeck / Docs / Insights Guide / GPU Insights / Namespace GPU Usage

Namespace GPU Usage

BeaverDeck uses this check to identify a specific gpu 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 typegpu-namespace-usage
Insights sectionGPU Insights
Alert severityInformational passing check

When It Reports A Finding

A selected namespace has one or more active GPU workload requests. BeaverDeck reports the total requested GPU count and whether a GPU quota exists.

Why This Is A Problem

This is inventory rather than a fault. It makes GPU ownership visible so operators can compare demand between namespaces and decide where quotas or capacity planning are needed.

Recommended Response

  1. Confirm that the reported requests match the namespace's expected workloads.
  2. Use the total as an input to quota, budget, and node-pool planning.
  3. Investigate stale or unexpected GPU workloads when the count is surprising.

Scope And Limitations

The check reports requested GPUs, not utilization or cost. It produces an OK status and does not require remediation by itself.

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