whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update horizontal-pod-autoscale-walkthrough.md

Browse Source 
pod is replaced with 'Pod' as per the documentation naming conventions.
This commit is contained in:
varadaprasanth
2020-09-15 15:22:59 +05:30
committed by GitHub
parent a0d7a841b8
commit 19d46f796d
1 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough.md
+5 -5
View File
@@ -11,7 +11,7 @@ weight: 100
<!-- overview --> <!-- overview -->
Horizontal Pod Autoscaler automatically scales the number of pods Horizontal Pod Autoscaler automatically scales the number of Pods
in a replication controller, deployment, replica set or stateful set based on observed CPU utilization in a replication controller, deployment, replica set or stateful set based on observed CPU utilization
(or, with beta support, on some other, application-provided metrics). (or, with beta support, on some other, application-provided metrics).
@@ -244,8 +244,8 @@ There are two other types of metrics, both of which are considered *custom metri
object metrics. These metrics may have names which are cluster specific, and require a more object metrics. These metrics may have names which are cluster specific, and require a more
advanced cluster monitoring setup. advanced cluster monitoring setup.
The first of these alternative metric types is *pod metrics*. These metrics describe pods, and The first of these alternative metric types is *pod metrics*. These metrics describe Pods, and
are averaged together across pods and compared with a target value to determine the replica count. are averaged together across Pods and compared with a target value to determine the replica count.
They work much like resource metrics, except that they *only* support a `target` type of `AverageValue`. They work much like resource metrics, except that they *only* support a `target` type of `AverageValue`.
Pod metrics are specified using a metric block like this: Pod metrics are specified using a metric block like this:
@@ -261,11 +261,11 @@ pods:
``` ```
The second alternative metric type is *object metrics*. These metrics describe a different The second alternative metric type is *object metrics*. These metrics describe a different
object in the same namespace, instead of describing pods. The metrics are not necessarily object in the same namespace, instead of describing Pods. The metrics are not necessarily
fetched from the object; they only describe it. Object metrics support `target` types of fetched from the object; they only describe it. Object metrics support `target` types of
both `Value` and `AverageValue`. With `Value`, the target is compared directly to the returned both `Value` and `AverageValue`. With `Value`, the target is compared directly to the returned
metric from the API. With `AverageValue`, the value returned from the custom metrics API is divided metric from the API. With `AverageValue`, the value returned from the custom metrics API is divided
by the number of pods before being compared to the target. The following example is the YAML by the number of Pods before being compared to the target. The following example is the YAML
representation of the `requests-per-second` metric. representation of the `requests-per-second` metric.
```yaml ```yaml