Skip to content

Commit 2d34007

Browse files
authored
Merge pull request #23900 from varadaprasanth/patch-4
Pod object is formatted
2 parents 02b9c7b + d455c7f commit 2d34007

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

content/en/docs/tasks/run-application/horizontal-pod-autoscale.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ weight: 90
1515

1616
<!-- overview -->
1717

18-
The Horizontal Pod Autoscaler automatically scales the number of pods
18+
The Horizontal Pod Autoscaler automatically scales the number of Pods
1919
in a replication controller, deployment, replica set or stateful set based on observed CPU utilization (or, with
2020
[custom metrics](https://git.k8s.io/community/contributors/design-proposals/instrumentation/custom-metrics-api.md)
2121
support, on some other application-provided metrics). Note that Horizontal
@@ -45,16 +45,16 @@ obtains the metrics from either the resource metrics API (for per-pod resource m
4545
or the custom metrics API (for all other metrics).
4646

4747
* For per-pod resource metrics (like CPU), the controller fetches the metrics
48-
from the resource metrics API for each pod targeted by the HorizontalPodAutoscaler.
48+
from the resource metrics API for each Pod targeted by the HorizontalPodAutoscaler.
4949
Then, if a target utilization value is set, the controller calculates the utilization
5050
value as a percentage of the equivalent resource request on the containers in
51-
each pod. If a target raw value is set, the raw metric values are used directly.
51+
each Pod. If a target raw value is set, the raw metric values are used directly.
5252
The controller then takes the mean of the utilization or the raw value (depending on the type
53-
of target specified) across all targeted pods, and produces a ratio used to scale
53+
of target specified) across all targeted Pods, and produces a ratio used to scale
5454
the number of desired replicas.
5555

56-
Please note that if some of the pod's containers do not have the relevant resource request set,
57-
CPU utilization for the pod will not be defined and the autoscaler will
56+
Please note that if some of the Pod's containers do not have the relevant resource request set,
57+
CPU utilization for the Pod will not be defined and the autoscaler will
5858
not take any action for that metric. See the [algorithm
5959
details](#algorithm-details) section below for more information about
6060
how the autoscaling algorithm works.
@@ -65,7 +65,7 @@ or the custom metrics API (for all other metrics).
6565
* For object metrics and external metrics, a single metric is fetched, which describes
6666
the object in question. This metric is compared to the target
6767
value, to produce a ratio as above. In the `autoscaling/v2beta2` API
68-
version, this value can optionally be divided by the number of pods before the
68+
version, this value can optionally be divided by the number of Pods before the
6969
comparison is made.
7070

7171
The HorizontalPodAutoscaler normally fetches metrics from a series of aggregated APIs (`metrics.k8s.io`,

0 commit comments

Comments
 (0)