All Tools View Categories About Contact Privacy

HPA Threshold Calculator

Plan CPU/memory utilization targets and replica counts for the HPA.

Runs entirely in your browser - nothing is uploaded and no cluster connection is made.
Your plan will appear here.

About HPA Threshold Calculator

The HPA Threshold Calculator helps you plan a Horizontal Pod Autoscaler. Enter a pod CPU and/or memory request, the target utilization percentage, and the expected total load. The tool reports the targetAverageUtilization and the replica count needed, clamped to your min/max.

Nothing is uploaded. The calculation runs entirely in your browser.

Features

  • Target utilisation - CPU and/or memory.
  • Replica math - load divided by per-replica capacity.
  • Min/max clamp - respects HPA bounds.
  • Copy / Download / Print - export the plan.

How to Use

  1. Enter pod request(s) and target %.
  2. Enter expected total load.
  3. Set min/max replicas.
  4. Click Calculate.

Examples

Example 1 - CPU. 100m request, 50% target, 1000m load => 20 replicas.

Example 2 - capped. Huge load clamped to max replicas.

Benefits

  • Right targets - avoid overload or waste.
  • Clamp aware - honours min/max.
  • Private - runs fully in the browser.
  • Exportable - copy, download or print.

Frequently Asked Questions

What does this calculator plan?
Given a pod CPU/memory request, a target utilization percentage and an expected total load, it computes the HPA targetAverageUtilization and the replica count required to serve the load.
What is targetAverageUtilization?
For a resource-based HPA it is the percentage of the pod request the autoscaler tries to maintain on average. The tool uses the percentage you enter.
How are replicas computed?
Expected load is divided by the per-replica capacity (request x target percent). The higher of the CPU and memory results drives the count, clamped to min/max replicas.
Does this connect to a cluster?
No. Enter your numbers; everything is computed in your browser.
Why plan HPA targets?
Good targets keep pods within limits while scaling cost-effectively and avoiding thrash.