Skip to content

Add AverageValue example for HPA resource metrics #53467

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
light0011 wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Add AverageValue example for HPA resource metrics #53467

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
a78bff6
Add AverageValue example for HPA resource metrics
light0011 Nov 27, 2025
a024d2b
Move AverageValue example to walkthrough doc
light0011 Dec 1, 2025
6cc6730
Move AverageValue example to walkthrough doc
light0011 Dec 1, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 25 additions & 0 deletions content/en/docs/tasks/run-application/horizontal-pod-autoscale.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -149,6 +149,31 @@ When a `targetAverageValue` or `targetAverageUtilization` is specified,
the `currentMetricValue` is computed by taking the average of the given
metric across all Pods in the HorizontalPodAutoscaler's scale target.

**Example: Scaling based on raw resource values**

You can configure the HPA to scale based on actual resource consumption without depending
on resource requests:
```yaml
type: Resource
resource:
name: cpu
target:
type: AverageValue
averageValue: 100m
---
type: Resource
resource:
name: memory
target:
type: AverageValue
averageValue: 512Mi
```

With `AverageValue`, the HPA scales based on the actual measured resource consumption per
pod, independent of any resource requests configured in the pod specification. For instance,
if the average CPU usage across all pods is 200m and the target averageValue is 100m, the
HPA will scale up according to the ratio (200m / 100m = 2.0).

Before checking the tolerance and deciding on the final values, the control
plane also considers whether any metrics are missing, and how many Pods
are [`Ready`](/docs/concepts/workloads/pods/pod-lifecycle/#pod-conditions).
Expand Down