ResourceQuota Calculator
Calculate the right ResourceQuota limits for CPU, memory and object counts per namespace.
About ResourceQuota Calculator
A namespace can have multiple independent ResourceQuota dimensions active simultaneously — CPU, memory, pod count, service count, and more. Hitting any single one blocks new object creation of that type, even if every other resource has ample headroom. This calculator surfaces remaining capacity per dimension and flags whichever resource is closest to its ceiling, since that's the one that will block work first.
Formula
remaining = quota - used
- Q
- Configured quota for the resource dimension
- U
- Current usage of that resource dimension
- R
- Remaining capacity before quota is exhausted
Worked example
With the default values below, ResourceQuota Calculator returns Most Constrained Resource of Services. Change any input above and every figure here is recalculated in your browser.
Inputs used
- CPU Quotaaccepts 0–100,000 cores
- 32 cores
- CPU Usedaccepts 0–100,000 cores
- 20 cores
- Memory Quotaaccepts 0–1,000,000 GiB
- 64 GiB
- Memory Usedaccepts 0–1,000,000 GiB
- 40 GiB
- Pods Quotaaccepts 0–1,000,000 pods
- 100 pods
- Pods Usedaccepts 0–1,000,000 pods
- 62 pods
- Services Quotaaccepts 0–100,000 services
- 20 services
- Services Usedaccepts 0–100,000 services
- 14 services
Results
- Most Constrained Resource
- Services
- CPU Remaining
- 12.00 cores
- Memory Remaining
- 24.00 GiB
- Pods Remaining
- 38 pods
- Services Remaining
- 6 services
Step by step
- 1CPU remaining= 12.00 cores
- 2Memory remaining= 24.00 GiB
- 3Pods remaining= 38
- 4Most constrained resource= Services at 70.0%
Assumptions and limits
- The result is derived only from the 8 inputs listed above. Anything not among them is not part of the calculation.
- In particular, this calculator does not take inflation, tax, fees or charges or compounding frequency into account.
- Figures are rounded for display to 2 decimal places, so totals built from several rounded parts can differ slightly from the unrounded arithmetic.
How these calculators are built and tested is described on the Methodology page. If a figure looks wrong, please report it.
Frequently Asked Questions
Can a namespace be blocked by pod count even with plenty of CPU/memory left?
Yes — the pods quota counts pod objects regardless of their resource requests, so a namespace running many small pods can exhaust its pod count quota while CPU and memory utilization remain low.
Why quota services separately from pods?
Services consume cluster-level resources like ClusterIPs and, for LoadBalancer-type services, cloud load balancer resources — capping service count prevents a single namespace from exhausting a shared, limited pool of those resources.
What's the best way to avoid quota surprises during deployments?
Monitor quota utilization continuously (not just at deploy time) and alert well before 100% on every dimension, since rolling updates and CronJob bursts can transiently spike pod count even when the steady-state usage is comfortably under quota.