Helm Chart Values Calculator
Calculate replica count and resource totals for a Helm release.
About Helm Chart Values Calculator
Replica count follows from throughput, with a floor of two so rolling updates and node failures do not cause an outage. Surge capacity must exist in the cluster or the update will stall. Rolling updates temporarily need more capacity than steady state, and a cluster sized exactly to steady state cannot complete a deployment.
Formula
Helm Chart Values
Replicas = target throughput ÷ per-pod throughput, minimum two for availability
- surge
- Extra pods created during a rolling update before old ones terminate
- minimum two
- A single replica cannot be updated without downtime
Worked example
With the default values below, Helm Chart Values Calculator returns Replica Count of 8. Change any input above and every figure here is recalculated in your browser.
Inputs used
- Target requests per secondminimum 0
- 1,200
- Requests per pod per secondminimum 0.01
- 150
- CPU request per podminimum 1 m
- 300 m
- Memory request per podminimum 1 MiB
- 512 MiB
- Rolling update surgeaccepts 0–100 %
- 25 %
Results
- Replica Count
- 8
- Total CPU Requested
- 2.400 cores
- Total Memory Requested
- 4.000 GiB
- Peak Replicas During Rolling Update
- 10
- Peak CPU During Update
- 3.000 cores
Step by step
- 1Values used
- 2Helm Chart Values
- 3Replica Count= 8
- 4Total CPU Requested= 2.400 cores
- 5Total Memory Requested= 4.000 GiB
- 6Peak Replicas During Rolling Update= 10
- 7Peak CPU During Update= 3.000 cores
Assumptions and limits
- The result is derived only from the 5 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 3 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
How is Helm Chart Values calculated?
Replicas = target throughput ÷ per-pod throughput, minimum two for availability Replica count follows from throughput, with a floor of two so rolling updates and node failures do not cause an outage. Surge capacity must exist in the cluster or the update will stall.
Why does Helm Chart Values matter?
Rolling updates temporarily need more capacity than steady state, and a cluster sized exactly to steady state cannot complete a deployment.
What values do I need to enter?
This calculator takes 5 inputs: Target requests per second, Requests per pod per second, CPU request per pod, Memory request per pod, Rolling update surge. The pre-filled defaults are a realistic starting point — replace them with figures from your own environment for a result you can act on.
Related Calculators
You might also need
- Database Connection Pool CalculatorCommonly used together
- Elasticsearch Shard CalculatorCommonly used together
- Redis Memory CalculatorCommonly used together
- Password GeneratorAlso in Developer & Networking
- Container Resource CalculatorAlso in Developer & Networking
- 4K Streaming DataAlso in Developer & Networking
