Deployment Capacity Calculator
Calculate the maximum pods a cluster's node pool can host and compare against current deployment replica utilization.
Inputs
Effective pods-per-node capacity, e.g. from the pod density calculator.
Total replicas currently running across all deployments in the cluster.
Max Cluster Pod Capacity
300pods
Current Utilization
40.0%
Spare Capacity
180pods
Capacity Exceeded
false
Step by step
Max pods = nodes × pods per node
10 × 30
= 300
Current utilization
120 ÷ 300
= 40.0%
Spare capacity
300 − 120
= 180 pods
How it works
Cluster-wide deployment capacity is bounded by node count multiplied by the effective pods-per-node ceiling (whichever of CPU, memory or kubelet max-pods binds tightest). Comparing current total replicas against that ceiling shows how much room remains before the cluster autoscaler needs to add nodes, or before pods start going Pending due to insufficient schedulable capacity.
Formula
maxPods = nodes × podsPerNode
- N
- Number of nodes in the cluster
- P_n
- Effective pods-per-node capacity
- P_{max}
- Maximum cluster pod capacity
Frequently Asked Questions
What utilization threshold should trigger adding nodes?
Most teams target 70-80% steady-state utilization, keeping 20-30% headroom for traffic spikes, rolling deployments and unscheduled pod restarts without waiting on cluster-autoscaler node provisioning time.
Does this account for DaemonSet and system pods?
No — subtract DaemonSet pods (CNI, log shippers, monitoring agents) per node from pods-per-node first, since they consume capacity on every node regardless of workload replicas.
How does this relate to the cluster autoscaler?
This calculator shows a static snapshot; pair it with the cluster autoscaler calculator to model how quickly new nodes come online once utilization crosses your scale-out threshold.