From c17803f912e1acdaa21198796345d1a9398f3632 Mon Sep 17 00:00:00 2001 From: Stewart-YU Date: Sat, 26 Aug 2017 03:59:22 +0800 Subject: [PATCH] Update cluster-management.md (#5130) Missing equal sign. --- docs/tasks/administer-cluster/cluster-management.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/tasks/administer-cluster/cluster-management.md b/docs/tasks/administer-cluster/cluster-management.md index 27c111fd9b..3566ef2c6f 100644 --- a/docs/tasks/administer-cluster/cluster-management.md +++ b/docs/tasks/administer-cluster/cluster-management.md @@ -71,7 +71,7 @@ If your cluster runs short on resources you can easily add more machines to it i If you're using GCE or GKE it's done by resizing Instance Group managing your Nodes. It can be accomplished by modifying number of instances on `Compute > Compute Engine > Instance groups > your group > Edit group` [Google Cloud Console page](https://console.developers.google.com) or using gcloud CLI: ```shell -gcloud compute instance-groups managed resize kubernetes-minion-group --size 42 --zone $ZONE +gcloud compute instance-groups managed resize kubernetes-minion-group --size=42 --zone=$ZONE ``` Instance Group will take care of putting appropriate image on new machines and start them, while Kubelet will register its Node with API server to make it available for scheduling. If you scale the instance group down, system will randomly choose Nodes to kill.