updated 07-bootstrapping-etcd

pull/709/head
Xander Grzywinski 2019-05-23 15:01:43 -07:00
parent f4be938cba
commit b03cb5ae94
1 changed files with 4 additions and 4 deletions

View File

@ -4,10 +4,11 @@ Kubernetes components are stateless and store cluster state in [etcd](https://gi
## Prerequisites
The commands in this lab must be run on each controller instance: `controller-0`, `controller-1`, and `controller-2`. Login to each controller instance using the `gcloud` command. Example:
The commands in this lab must be run on each controller instance: `controller-0`, `controller-1`, and `controller-2`. Login to each controller instance using `ssh`. Example:
```
gcloud compute ssh controller-0
EXTERNAL_IP=$(az vm show --show-details -g kubernetes-the-hard-way -n controller-0 --output tsv | cut -f19)
ssh azureuser@${EXTERNAL_IP}
```
### Running commands in parallel with tmux
@ -46,8 +47,7 @@ Extract and install the `etcd` server and the `etcdctl` command line utility:
The instance internal IP address will be used to serve client requests and communicate with etcd cluster peers. Retrieve the internal IP address for the current compute instance:
```
INTERNAL_IP=$(curl -s -H "Metadata-Flavor: Google" \
http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/ip)
INTERNAL_IP=$(curl -H Metadata:true "http://169.254.169.254/metadata/instance/network/interface/0/ipv4/ipAddress/0/privateIpAddress?api-version=2017-08-01&format=text")
```
Each etcd member must have a unique name within an etcd cluster. Set the etcd name to match the hostname of the current compute instance: