From b87603b556e2871bcaaf67e465d11e92440558cc Mon Sep 17 00:00:00 2001 From: Ken'ichi Ohmichi Date: Wed, 1 Aug 2018 15:45:28 -0700 Subject: [PATCH] Trivial: Update HPA description (#9711) * Trivial: Remove unnecessary new line Current HPA page[1] contains unnecessary new line between "metrics.k8s.io" and "custom.metrics.k8s.io", but that does not have any meaning. This removes it for the readability. [1]: https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale * Trivial: Replace RC with RS for HPA doc As RC doc[1], RS is now the recommended way to set up replication. So this replaces RC with RS for HPA doc. [1]: https://kubernetes.io/docs/concepts/workloads/controllers/replicationcontroller/ --- .../docs/tasks/run-application/horizontal-pod-autoscale.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/en/docs/tasks/run-application/horizontal-pod-autoscale.md b/content/en/docs/tasks/run-application/horizontal-pod-autoscale.md index a2ae359d17..3bff9a2196 100644 --- a/content/en/docs/tasks/run-application/horizontal-pod-autoscale.md +++ b/content/en/docs/tasks/run-application/horizontal-pod-autoscale.md @@ -60,7 +60,7 @@ or the custom metrics API (for all other metrics). * For object metrics, a single metric is fetched (which describes the object in question), and compared to the target value, to produce a ratio as above. -The HorizontalPodAutoscaler normally fetches metrics from a series of aggregated APIs (`metrics.k8s.io`,\ +The HorizontalPodAutoscaler normally fetches metrics from a series of aggregated APIs (`metrics.k8s.io`, `custom.metrics.k8s.io`, and `external.metrics.k8s.io`). It can also fetch metrics directly from Heapster. Fetching metrics from Heapster is deprecated as of Kubernetes 1.11. @@ -92,8 +92,8 @@ We can list autoscalers by `kubectl get hpa` and get detailed description by `ku Finally, we can delete an autoscaler using `kubectl delete hpa`. In addition, there is a special `kubectl autoscale` command for easy creation of a Horizontal Pod Autoscaler. -For instance, executing `kubectl autoscale rc foo --min=2 --max=5 --cpu-percent=80` -will create an autoscaler for replication controller *foo*, with target CPU utilization set to `80%` +For instance, executing `kubectl autoscale rs foo --min=2 --max=5 --cpu-percent=80` +will create an autoscaler for replication set *foo*, with target CPU utilization set to `80%` and the number of replicas between 2 and 5. The detailed documentation of `kubectl autoscale` can be found [here](/docs/reference/generated/kubectl/kubectl-commands/#autoscale).