Namespace Quota Calculator
Work out namespace quota instantly with clear inputs, formula shown and shareable results.
About Namespace Quota Calculator
ResourceQuota caps the total requests a namespace may make, which is how a shared cluster stops one team consuming everything. Dividing available capacity evenly is the starting point; because teams rarely peak simultaneously, quotas are usually overcommitted to around 150 percent of a strict share, with monitoring on actual aggregate usage rather than allocated quota.
Formula
Quota allocation
available = cluster capacity x (1 - system reserve); per namespace = available / namespaces; overcommitted quota = per namespace x factor
Worked example
With the default values below, Namespace Quota Calculator returns CPU quota per namespace of 14.17. Change any input above and every figure here is recalculated in your browser.
Inputs used
- Cluster allocatable CPUminimum 0.1 cores
- 200 cores
- Cluster allocatable memoryminimum 0.1 GB
- 800 GB
- Namespaces sharing the clusterminimum 1
- 12
- Reserved for system namespacesaccepts 0–60 %
- 15 %
Results
- CPU quota per namespace
- 14.17 cores
- Memory quota per namespace
- 56.67 GB
- Cores reserved for system namespaces
- 30.0 cores
- Quota if overcommitted at 150 percent
- 21.25 cores
Step by step
- 1Values used
- 2Quota allocation
- 3CPU quota per namespace= 14.17 cores
- 4Memory quota per namespace= 56.67 GB
- 5Cores reserved for system namespaces= 30.0 cores
- 6Quota if overcommitted at 150 percent= 21.25 cores
Assumptions and limits
- The result is derived only from the 4 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
Should quotas apply to requests or limits?
Both, with different values. Quota on requests controls scheduling capacity; quota on limits controls the worst-case burst a namespace can create.
What happens when a namespace hits its quota?
New pods are rejected at admission with a clear error. That is far better than the alternative of one namespace starving the cluster.
Related Calculators
- Auto Scaling Instance Count Calculator
- Availability Zone Redundancy Cost Calculator
- BigQuery Slot Estimate Calculator
- Budget Alert Threshold Calculator
- Cache Node Sizing Calculator
- CDN Cost Calculator
- Cloud Exit Cost Calculator
- Cloud Monthly Cost Calculator
- Cloud SLA Composite Availability Calculator
- Cluster Autoscaler Sizing Calculator
You might also need
- Cache Node Sizing CalculatorAlso in Cloud Sizing & Cost
- CDN Cost CalculatorAlso in Cloud Sizing & Cost
- Cloud Exit Cost CalculatorAlso in Cloud Sizing & Cost
- Cloud Monthly Cost CalculatorAlso in Cloud Sizing & Cost
- Cluster Autoscaler Sizing CalculatorAlso in Cloud Sizing & Cost
- Database Storage Sizing CalculatorAlso in Cloud Sizing & Cost
