kubernetes
/
website
mirror of https://github.com/kubernetes/website.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Operating etcd cluster for Kubernetes bad format in the final page (#6056) 

* Operating etcd cluster for Kubernetes bad format in the final page

* Update configure-upgrade-etcd.md

* Update configure-upgrade-etcd.md
reviewable/pr6064/r1
chenhonggc 2017-10-26 11:43:06 -05:00 committed by Steve Perry
parent 67135553e7
commit 2a7bffb839
1 changed files with 6 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
docs/tasks/administer-cluster/configure-upgrade-etcd.md
View File

@ -40,9 +40,7 @@ Use a single-node etcd cluster only for testing purpose.
1. Run the following: 1. Run the following:
``` bash ./etcd --client-listen-urls=http://$PRIVATE_IP:2379 --client-advertise-urls=http://$PRIVATE_IP:2379
./etcd --client-listen-urls=http://$PRIVATE_IP:2379 --client-advertise-urls=http://$PRIVATE_IP:2379
```
2. Start Kubernetes API server with the flag `--etcd-servers=$PRIVATE_IP:2379`. 2. Start Kubernetes API server with the flag `--etcd-servers=$PRIVATE_IP:2379`.
@ -130,12 +128,11 @@ Though etcd keeps unique member IDs internally, it is recommended to use a uniqu
4. Start the newly added member on a machine with the IP `10.0.0.4`: 4. Start the newly added member on a machine with the IP `10.0.0.4`:
```bash export ETCD_NAME="member4"
export ETCD_NAME="member4" export ETCD_INITIAL_CLUSTER="member2=http://10.0.0.2:2380,member3=http://10.0.0.3:2380,member4=http://10.0.0.4:2380"
export ETCD_INITIAL_CLUSTER="member2=http://10.0.0.2:2380,member3=http://10.0.0.3:2380,member4=http://10.0.0.4:2380" export ETCD_INITIAL_CLUSTER_STATE=existing
export ETCD_INITIAL_CLUSTER_STATE=existing etcd [flags]
etcd [flags]
```
5. Do either of the following: 5. Do either of the following:
1. Update its `--etcd-servers` flag to make Kubernetes aware of the configuration changes, then restart the Kubernetes API server. 1. Update its `--etcd-servers` flag to make Kubernetes aware of the configuration changes, then restart the Kubernetes API server.