From ef4359ab7e6789ce250232cb302842638d81c000 Mon Sep 17 00:00:00 2001 From: Sergey Tiraspolsky Date: Mon, 4 Jan 2016 17:08:50 -0800 Subject: [PATCH] Fix cluster management doc Update cluster management doc with correct command to resize cluster --- docs/admin/cluster-management.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/admin/cluster-management.md b/docs/admin/cluster-management.md index 8b17b1f2ebf..1eb8ea49fc7 100644 --- a/docs/admin/cluster-management.md +++ b/docs/admin/cluster-management.md @@ -91,7 +91,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: ``` -gcloud compute instance-groups managed --zone $ZONE resize my-cluster-minon-group --new-size 42 +gcloud compute instance-groups managed resize kubernetes-minion-group --size 42 ``` 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.