Calculate the right ResourceQuota limits for CPU, memory and object counts per namespace.
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.
remaining = quota - used
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.
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.
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.