whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge pull request #811 from justinsb/multizone_fixes

Browse Source 
Two minor fixes to multizone doc
This commit is contained in:
Phillip Wittrock
2016-07-15 08:22:21 -07:00
committed by GitHub
parent 2a1f7744ce 272814cdb2
commit 41374496e9
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/admin/multiple-zones.md
+2 -2
View File
@@ -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 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). 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 kube-up will not create a new master, but will reuse one that was previously
created instead. created instead.
@@ -183,7 +183,7 @@ EOF
The PV is also labeled with the zone & region it was created in. For 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 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).) be improved in a future version (issue [#23330](https://github.com/kubernetes/kubernetes/issues/23330).)
```shell ```shell