Sum up total CPU and memory consumption across all workloads in a namespace.
A ResourceQuota caps the total requests and limits summed across every pod in a namespace, preventing one team from starving others sharing the cluster. This calculator multiplies per-pod requests by pod count to get namespace totals, then compares those totals against the configured CPU and memory quotas so you can see utilization before the API server starts rejecting new pod creations.
Total CPU request
totalCPU = pods × perPodCPU
Quota utilization
cpuQuotaUsed% = (totalCPU / quotaCPU) × 100
The API server rejects any new pod (or object with a resource request) that would push the namespace total above quota, returning a 403 Forbidden with a quota-exceeded message — existing pods are not evicted.
You can configure quotas separately for requests.cpu/requests.memory and limits.cpu/limits.memory, plus object counts like pods, services and persistentvolumeclaims — this calculator models the requests side.
Leave 15-20% headroom below the hard quota for rolling deployments, since a new ReplicaSet's pods briefly coexist with the old ones during a rollout and temporarily double-count requests.