From 0e4aa4968514c2c19e027336578a5cd7b309e942 Mon Sep 17 00:00:00 2001 From: Emilian Losneanu Date: Tue, 18 Jul 2017 14:31:02 +0300 Subject: [PATCH 1/2] Mention how to ssh first time we need to ssh --- docs/04-etcd.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/04-etcd.md b/docs/04-etcd.md index 69897d8..4157a63 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`: +You connect to each controller wit `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. From f312a1c52adbe5d24e65ca24730e8fe051775b7a Mon Sep 17 00:00:00 2001 From: Emilian Losneanu Date: Tue, 18 Jul 2017 14:35:05 +0300 Subject: [PATCH 2/2] Update 04-etcd.md --- docs/04-etcd.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/04-etcd.md b/docs/04-etcd.md index 4157a63..f37f117 100644 --- a/docs/04-etcd.md +++ b/docs/04-etcd.md @@ -21,7 +21,7 @@ However, all the e2e tested configurations currently run etcd on the master node Run the following commands on `controller0`, `controller1`, `controller2`: -You connect to each controller wit `gcloud compute ssh` command. +You connect to each controller with `gcloud compute ssh` command. ### TLS Certificates