From b8aa4c661083b9dede37ebac2e4cae7239492da3 Mon Sep 17 00:00:00 2001 From: yupengzte Date: Mon, 27 Mar 2017 10:26:11 +0800 Subject: [PATCH] Delete the useless spaces Signed-off-by: yupengzte --- docs/admin/cluster-management.md | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/docs/admin/cluster-management.md b/docs/admin/cluster-management.md index 8b2c3feb3b..f15cde21b8 100644 --- a/docs/admin/cluster-management.md +++ b/docs/admin/cluster-management.md @@ -19,7 +19,7 @@ To install Kubernetes on a set of machines, consult one of the existing [Getting ## Upgrading a cluster -The current state of cluster upgrades is provider dependent, and some releases may require special care when upgrading. It is recommended that administrators consult both the [release notes](https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG.md), as well as the version specific upgrade notes prior to upgrading their clusters. +The current state of cluster upgrades is provider dependent, and some releases may require special care when upgrading. It is recommended that administrators consult both the [release notes](https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG.md), as well as the version specific upgrade notes prior to upgrading their clusters. * [Upgrading to 1.6](/docs/admin/upgrade-1-6) @@ -58,12 +58,12 @@ The node upgrade process is user-initiated and is described in the [GKE document ### Upgrading clusters on other platforms -Different providers, and tools, will manage upgrades differently. It is recommended that you consult their main documentation regarding upgrades. +Different providers, and tools, will manage upgrades differently. It is recommended that you consult their main documentation regarding upgrades. * [kops](https://github.com/kubernetes/kops) * [kargo](https://github.com/kubernetes-incubator/kargo) * [CoreOS Tectonic](https://coreos.com/tectonic/docs/latest/admin/upgrade.html) -* ... +* ... ## Resizing a cluster @@ -78,7 +78,6 @@ Instance Group will take care of putting appropriate image on new machines and s In other environments you may need to configure the machine yourself and tell the Kubelet on which machine API server is running. - ### Cluster autoscaling If you are using GCE or GKE, you can configure your cluster so that it is automatically rescaled based on @@ -97,7 +96,7 @@ an extended period of time (10min but it may change in the future). Cluster autoscaler is configured per instance group (GCE) or node pool (GKE). -If you are using GCE then you can either enable it while creating a cluster with kube-up.sh script. +If you are using GCE then you can either enable it while creating a cluster with kube-up.sh script. To configure cluster autoscaler you have to set three environment variables: * `KUBE_ENABLE_CLUSTER_AUTOSCALER` - it enables cluster autoscaler if set to true.