From 1b0fafbbe061fe317ea966b91a225771790166bc Mon Sep 17 00:00:00 2001 From: hellwen Date: Fri, 9 Sep 2016 18:17:17 +0800 Subject: [PATCH 1/2] Update volumes.md --- docs/user-guide/volumes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/user-guide/volumes.md b/docs/user-guide/volumes.md index 4d753ca308..d4d20e3e47 100644 --- a/docs/user-guide/volumes.md +++ b/docs/user-guide/volumes.md @@ -10,7 +10,7 @@ assignees: On-disk files in a container are ephemeral, which presents some problems for non-trivial applications when running in containers. First, when a container crashes kubelet will restart it, but the files will be lost - the -container starts with a clean slate. Second, when running containers together +container starts with a clean state. Second, when running containers together in a `Pod` it is often necessary to share files between those containers. The Kubernetes `Volume` abstraction solves both of these problems. From ef63728e6298f4837f264996d82d76994959cb7b Mon Sep 17 00:00:00 2001 From: CJ Cullen Date: Mon, 12 Sep 2016 11:01:03 -0700 Subject: [PATCH 2/2] Remove `=true` from gcloud commands --- docs/admin/cluster-management.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/admin/cluster-management.md b/docs/admin/cluster-management.md index 1be4fc8a02..c681a45996 100644 --- a/docs/admin/cluster-management.md +++ b/docs/admin/cluster-management.md @@ -111,11 +111,11 @@ to the corresponding `gcloud` commands. Examples: ```shell -gcloud container clusters create mytestcluster --zone=us-central1-b --enable-autoscaling=true --min-nodes=3 --max-nodes=10 --num-nodes=5 +gcloud container clusters create mytestcluster --zone=us-central1-b --enable-autoscaling --min-nodes=3 --max-nodes=10 --num-nodes=5 ``` ```shell -gcloud container clusters update mytestcluster --enable-autoscaling=true --min-nodes=1 --max-nodes=15 +gcloud container clusters update mytestcluster --enable-autoscaling --min-nodes=1 --max-nodes=15 ``` **Cluster autoscaler expects that nodes have not been manually modified (e.g. by adding labels via kubectl) as those properties would not be propagated to the new nodes within the same instance group.**