From 272814cdb2f917702b877f5f89b5dcb58d801061 Mon Sep 17 00:00:00 2001 From: Justin Santa Barbara Date: Sun, 10 Jul 2016 17:36:55 -0400 Subject: [PATCH] Two minor fixes to multizone doc --- docs/admin/multiple-zones.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/admin/multiple-zones.md b/docs/admin/multiple-zones.md index e420bda304..3dd135b046 100644 --- a/docs/admin/multiple-zones.md +++ b/docs/admin/multiple-zones.md @@ -117,7 +117,7 @@ kubernetes-minion-a12q Ready 6m beta.kubernetes.io Let's add another set of nodes to the existing cluster, reusing the existing master, running in a different zone (us-central1-b or us-west-2b). -We run kube-up again, but by specifying `KUBE_USE_EXISTING_MASTER=1` +We run kube-up again, but by specifying `KUBE_USE_EXISTING_MASTER=true` kube-up will not create a new master, but will reuse one that was previously created instead. @@ -183,7 +183,7 @@ EOF The PV is also labeled with the zone & region it was created in. For version 1.2, dynamic persistent volumes are always created in the zone -of the cluster master (here us-centaral1-a / us-west-2a); this will +of the cluster master (here us-central1-a / us-west-2a); this will be improved in a future version (issue [#23330](https://github.com/kubernetes/kubernetes/issues/23330).) ```shell