From f17e19fae7dc097ec477e3c6ddb1def32913617d Mon Sep 17 00:00:00 2001 From: Catherine Luse Date: Mon, 6 Jul 2020 13:36:02 -0700 Subject: [PATCH] Edit formatting on cluster autoscaler page --- .../cluster-autoscaler/_index.md | 24 ++++++++++++------- 1 file changed, 15 insertions(+), 9 deletions(-) diff --git a/content/rancher/v2.x/en/cluster-admin/cluster-autoscaler/_index.md b/content/rancher/v2.x/en/cluster-admin/cluster-autoscaler/_index.md index 819d8152efd..4f1d2e14430 100644 --- a/content/rancher/v2.x/en/cluster-admin/cluster-autoscaler/_index.md +++ b/content/rancher/v2.x/en/cluster-admin/cluster-autoscaler/_index.md @@ -1,19 +1,25 @@ --- -title: Cluster autoscaler +title: Cluster Autoscaler weight: 1 --- -This doc will guide you how to install and use [k8s cluster-autoscaler](https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/) on Rancher custom clusters using AWS EC2 Auto Scaling Groups. +In this section, you'll learn how to install and use the [Kubernetes cluster-autoscaler](https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/) on Rancher custom clusters using AWS EC2 Auto Scaling Groups. -Cluster Autoscaler is a tool that automatically adjusts the size of the k8s cluster when one of the following conditions is true: +The cluster autoscaler is a tool that automatically adjusts the size of the Kubernetes cluster when one of the following conditions is true: -* there are pods that failed to run in the cluster due to insufficient resources, -* there are nodes in the cluster that have been underutilized for an extended period of time and their pods can be placed on other existing nodes. +* There are pods that failed to run in the cluster due to insufficient resources. +* There are nodes in the cluster that have been underutilized for an extended period of time and their pods can be placed on other existing nodes. -Cluster Autoscaler is designed to run on k8s master nodes. It's possible to run a customized deployment of Cluster Autoscaler on worker nodes, but extra care needs to be taken to ensure that Cluster Autoscaler remains up and running. Users can put it into kube-system namespace (Cluster Autoscaler doesn't scale down node with non-mirrored kube-system pods running on them) and set a priorityClassName: system-cluster-critical property on your pod spec (to prevent your pod from being evicted). +To prevent your pod from being evicted, set a `priorityClassName: system-cluster-critical` property on your pod spec. -Cluster Autoscaler is providing support to distinct cloud providers, more info at [cluster-autoscaler supported cloud providers](https://github.com/kubernetes/autoscaler/tree/master/cluster-autoscaler#deployment) +Cluster Autoscaler is designed to run on Kubernetes master nodes. It can run in the `kube-system` namespace. Cluster Autoscaler doesn't scale down nodes with non-mirrored `kube-system` pods running on them. -### Setting up the cluster autoscaler on Amazon Cloud Provider +It's possible to run a customized deployment of Cluster Autoscaler on worker nodes, but extra care needs to be taken to ensure that Cluster Autoscaler remains up and running. -For details on running the cluster autoscaler on Amazon cloud provider, refer to [this page.]({{}}/rancher/v2.x/en/cluster-autoscaler/amazon) \ No newline at end of file +# Cloud Providers + +Cluster Autoscaler provides support to distinct cloud providers. For more information, go to [cluster-autoscaler supported cloud providers.](https://github.com/kubernetes/autoscaler/tree/master/cluster-autoscaler#deployment) + +### Setting up Cluster Autoscaler on Amazon Cloud Provider + +For details on running the cluster autoscaler on Amazon cloud provider, refer to [this page.]({{}}/rancher/v2.x/en/cluster-admin/cluster-autoscaler/amazon)