# Bootstrapping the etcd Cluster Kubernetes components are stateless and store cluster state in [etcd](https://github.com/coreos/etcd). In this lab you will bootstrap a three node etcd cluster and configure it for high availability and secure remote access. ## 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: ``` gcloud compute ssh controller-0 ``` ## Bootstrapping an etcd Cluster Member ### Download and Install the etcd Binaries Download the official etcd release binaries from the [coreos/etcd](https://github.com/coreos/etcd) GitHub project: ``` wget -q --show-progress --https-only --timestamping \ "https://github.com/coreos/etcd/releases/download/v3.2.11/etcd-v3.2.11-linux-amd64.tar.gz" ``` Extract and install the `etcd` server and the `etcdctl` command line utility: ``` tar -xvf etcd-v3.2.11-linux-amd64.tar.gz ``` ``` sudo mv etcd-v3.2.11-linux-amd64/etcd* /usr/local/bin/ ``` ### Configure the etcd Server ``` sudo mkdir -p /etc/etcd /var/lib/etcd ``` ``` sudo cp ca.pem kubernetes-key.pem kubernetes.pem /etc/etcd/ ``` 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) ``` 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: ``` ETCD_NAME=$(hostname -s) ``` Create the `etcd.service` systemd unit file: ``` cat > etcd.service < Remember to run the above commands on each controller node: `controller-0`, `controller-1`, and `controller-2`. ## Verification List the etcd cluster members: ``` ETCDCTL_API=3 etcdctl member list ``` > output ``` 3a57933972cb5131, started, controller-2, https://10.240.0.12:2380, https://10.240.0.12:2379 f98dc20bce6225a0, started, controller-0, https://10.240.0.10:2380, https://10.240.0.10:2379 ffed16798470cab5, started, controller-1, https://10.240.0.11:2380, https://10.240.0.11:2379 ``` Next: [Bootstrapping the Kubernetes Control Plane](08-bootstrapping-kubernetes-controllers.md)