From 2a7bffb839b7543f96dfcd04498c2a5bd5f91988 Mon Sep 17 00:00:00 2001 From: chenhonggc Date: Thu, 26 Oct 2017 11:43:06 -0500 Subject: [PATCH] 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 --- .../administer-cluster/configure-upgrade-etcd.md | 15 ++++++--------- 1 file changed, 6 insertions(+), 9 deletions(-) diff --git a/docs/tasks/administer-cluster/configure-upgrade-etcd.md b/docs/tasks/administer-cluster/configure-upgrade-etcd.md index 97253f00a0..ce2f3652a2 100644 --- a/docs/tasks/administer-cluster/configure-upgrade-etcd.md +++ b/docs/tasks/administer-cluster/configure-upgrade-etcd.md @@ -40,9 +40,7 @@ Use a single-node etcd cluster only for testing purpose. 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`. @@ -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`: - ```bash - 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_STATE=existing - etcd [flags] - ``` + 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_STATE=existing + etcd [flags] + 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.