ResourceQuota Calculator
Calculate the right ResourceQuota limits for CPU, memory and object counts per namespace.
Inputs
Most Constrained Resource
Services
CPU Remaining
12.00cores
Memory Remaining
24.00GiB
Pods Remaining
38pods
Services Remaining
6services
Step by step
CPU remaining
32 − 20
= 12.00 cores
Memory remaining
64 − 40
= 24.00 GiB
Pods remaining
100 − 62
= 38
Most constrained resource
highest utilization%
= Services at 70.0%
How it works
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
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.