From 0d8345e0c1fbb75820028530ffebe5b7a600a255 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=C3=85smund=20Grammeltvedt?= Date: Thu, 6 Nov 2014 10:44:49 +0100 Subject: [PATCH] Fix typo in docs Suggesting that users add two nodes with the same name is probably not a good idea. --- Documentation/security.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/security.md b/Documentation/security.md index 5686c1190..c170f988f 100644 --- a/Documentation/security.md +++ b/Documentation/security.md @@ -124,7 +124,7 @@ DISCOVERY_URL=... # from https://discovery.etcd.io/new etcd -name node1 -data-dir node1 -ca-file=/path/to/ca.crt -cert-file=/path/to/node1.crt -key-file=/path/to/node1.key -peer-addr ${node1_public_ip}:7001 -discovery ${DISCOVERY_URL} # Node2 -etcd -name node1 -data-dir node2 -ca-file=/path/to/ca.crt -cert-file=/path/to/node2.crt -key-file=/path/to/node2.key -peer-addr ${node2_public_ip}:7001 -discovery ${DISCOVERY_URL} +etcd -name node2 -data-dir node2 -ca-file=/path/to/ca.crt -cert-file=/path/to/node2.crt -key-file=/path/to/node2.key -peer-addr ${node2_public_ip}:7001 -discovery ${DISCOVERY_URL} ``` The etcd nodes will form a cluster and all communication between nodes in the cluster will be encrypted and authenticated using the client certificates. You will see in the output of etcd that the addresses it connects to use HTTPS.