From 19d46f796d87a3daa748413161d6a91c08c4a76a Mon Sep 17 00:00:00 2001 From: varadaprasanth <48983411+varadaprasanth@users.noreply.github.com> Date: Tue, 15 Sep 2020 15:22:59 +0530 Subject: [PATCH] Update horizontal-pod-autoscale-walkthrough.md pod is replaced with 'Pod' as per the documentation naming conventions. --- .../horizontal-pod-autoscale-walkthrough.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/content/en/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough.md b/content/en/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough.md index 2c00e4aa7b..9c8e1f8951 100644 --- a/content/en/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough.md +++ b/content/en/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough.md @@ -11,7 +11,7 @@ weight: 100 -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 (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 advanced cluster monitoring setup. -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. +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. 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: @@ -261,11 +261,11 @@ pods: ``` 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 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 -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. ```yaml