<p>Is there a way that I can access the <code>etcd</code> endpoints from <code>kubernetes</code> master node without actually getting into <code>etcd</code> cluster? </p>

<p>For a example, can I do a health curl (using <code>ssh</code>) to <code>etcd</code> endpoints or see endpoints and get the return status <strong>from the kubernetes master node? (i.e. without really getting inside the <code>etcd</code> master)</strong></p>

IT17157124 Jayarathna K.M.J.B.
<p>it really depends on how you configured the cluster. Actually, etcd cluster could work outside of k8s cluster at all. Also etcd could be configurred with TLS auth, so you will need to provide cert files to be able make any request via curl. <code>etcdctl</code> does everything you need. Something like:</p>
<pre><code>~# export ETCDCTL_API=3
~# export ETCDCTL_ENDPOINTS=https://kub01.msk.test.ru:2379,https://kub02.msk.test.ru:2379,https://kub03.msk.test.ru:2379
~# etcdctl endpoint status
https://kub01.msk.test.ru:2379, e9bc9d307c96fd08, 3.3.13, 10 MB, true, 1745, 17368976
https://kub02.msk.test.ru:2379, 885ed66440d63a79, 3.3.13, 10 MB, false, 1745, 17368976
https://kub03.msk.test.ru:2379, 8c5c20ece034a652, 3.3.13, 10 MB, false, 1745, 17368976
</code></pre>
<p>or with the TLS:</p>
<pre><code>~# etcdctl endpoint health
client: etcd cluster is unavailable or misconfigured; error #0: remote error: tls: bad certificate
; error #1: remote error: tls: bad certificate
; error #2: remote error: tls: bad certificate

# need to export environment vars

~# export ETCDCTL_CACERT=&lt;PATH_TO_FILE&gt;
~# export ETCDCTL_CERT=&lt;PATH_TO_FILE&gt;
~# export ETCDCTL_KEY=&lt;PATH_TO_FILE&gt;
~# etcdctl endpoint health
https://kub01.msk.test.ru:2379 is healthy: successfully committed proposal: took = 2.946423ms
https://kub02.msk.test.ru:2379 is healthy: successfully committed proposal: took = 1.5883ms
https://kub03.msk.test.ru:2379 is healthy: successfully committed proposal: took = 1.745591ms
</code></pre>
