Update for clarity (#10909)

We receive a lot of customer queries around HPA not communicating with metrics-server where the core issue is that metrics-server is not installed. Feedback has been that this wasn't explicitly clear, suggesting this change in wording to assist.
This commit is contained in:
Kevin Morgan
2018-11-11 19:05:26 -08:00
committed by k8s-ci-robot
parent 8d8c55a8d5
commit 897c02e36e
@@ -25,9 +25,8 @@ This document walks you through an example of enabling Horizontal Pod Autoscaler
This example requires a running Kubernetes cluster and kubectl, version 1.2 or later. This example requires a running Kubernetes cluster and kubectl, version 1.2 or later.
[metrics-server](https://github.com/kubernetes-incubator/metrics-server/) monitoring needs to be deployed in the cluster [metrics-server](https://github.com/kubernetes-incubator/metrics-server/) monitoring needs to be deployed in the cluster
to provide metrics via the resource metrics API, as Horizontal Pod Autoscaler uses this API to collect metrics to provide metrics via the resource metrics API, as Horizontal Pod Autoscaler uses this API to collect metrics. The instructions for deploying this are on the GitHub repository of [metrics-server](https://github.com/kubernetes-incubator/metrics-server/), if you followed [getting started on GCE guide](/docs/setup/turnkey/gce/),
(if you followed [getting started on GCE guide](/docs/setup/turnkey/gce/), metrics-server monitoring will be turned-on by default.
metrics-server monitoring will be turned-on by default).
To specify multiple resource metrics for a Horizontal Pod Autoscaler, you must have a Kubernetes cluster To specify multiple resource metrics for a Horizontal Pod Autoscaler, you must have a Kubernetes cluster
and kubectl at version 1.6 or later. Furthermore, in order to make use of custom metrics, your cluster and kubectl at version 1.6 or later. Furthermore, in order to make use of custom metrics, your cluster