From f83b95234a70fc8bfec6697c0267b1120203e2be Mon Sep 17 00:00:00 2001 From: Dominic001 Date: Fri, 28 Oct 2016 22:49:17 +0200 Subject: [PATCH 1/2] more explicit etcdctl description assuming that kubernetes is almost always used with docker. In case other container solutions as lxc are integrated this section will need further revision. Just using the bare etcl command is a bit too less, at least there should be a hint that you log in into the container. --- docs/admin/high-availability/index.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/admin/high-availability/index.md b/docs/admin/high-availability/index.md index efe6ddac4b..62da7f7eb9 100644 --- a/docs/admin/high-availability/index.md +++ b/docs/admin/high-availability/index.md @@ -100,16 +100,16 @@ for `${NODE_IP}` on each machine. #### Validating your cluster -Once you copy this into all three nodes, you should have a clustered etcd set up. You can validate with +Once you copy this into all three nodes, you should have a clustered etcd set up. In case you run your pods on docker container you can validate with ```shell -etcdctl member list +docker exec -i -t < container_id > etcdctl member list ``` and ```shell -etcdctl cluster-health +docker exec -i -t < container_id > etcdctl cluster-health ``` You can also validate that this is working with `etcdctl set foo bar` on one node, and `etcdctl get foo` From f6f0da2f9af5b93e0e31bb286cc9705945df3062 Mon Sep 17 00:00:00 2001 From: Dominic001 Date: Sat, 29 Oct 2016 01:48:34 +0200 Subject: [PATCH 2/2] more generic patch use kubectl exec command so we dont have to worry about container type --- docs/admin/high-availability/index.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/docs/admin/high-availability/index.md b/docs/admin/high-availability/index.md index 62da7f7eb9..ad78270e4a 100644 --- a/docs/admin/high-availability/index.md +++ b/docs/admin/high-availability/index.md @@ -100,16 +100,15 @@ for `${NODE_IP}` on each machine. #### Validating your cluster -Once you copy this into all three nodes, you should have a clustered etcd set up. In case you run your pods on docker container you can validate with - +Once you copy this into all three nodes, you should have a clustered etcd set up. You can validate on master with ```shell -docker exec -i -t < container_id > etcdctl member list +kubectl exec < pod_name > etcdctl member list ``` and ```shell -docker exec -i -t < container_id > etcdctl cluster-health +kubectl exec < pod_name > etcdctl cluster-health ``` You can also validate that this is working with `etcdctl set foo bar` on one node, and `etcdctl get foo`