From 19a249c402f51bc33bab06be517e729391a8d926 Mon Sep 17 00:00:00 2001 From: MBuege Date: Thu, 15 Jun 2017 12:13:03 +0200 Subject: [PATCH] add hint to "gcloud ssh" where it is first needed --- docs/04-etcd.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/04-etcd.md b/docs/04-etcd.md index 69897d8..85d6296 100644 --- a/docs/04-etcd.md +++ b/docs/04-etcd.md @@ -21,6 +21,8 @@ However, all the e2e tested configurations currently run etcd on the master node Run the following commands on `controller0`, `controller1`, `controller2`: +> Login to each machine using the gcloud compute ssh command + ### TLS Certificates The TLS certificates created in the [Setting up a CA and TLS Cert Generation](02-certificate-authority.md) lab will be used to secure communication between the Kubernetes API server and the etcd cluster. The TLS certificates will also be used to limit access to the etcd cluster using TLS client authentication. Only clients with a TLS certificate signed by a trusted CA will be able to access the etcd cluster.