<p>I am check etcd(3.3.13) cluster status using this command:</p>

<pre><code>[root@iZuf63refzweg1d9dh94t8Z work]# /opt/k8s/bin/etcdctl endpoint health --cluster
https://172.19.150.82:2379 is unhealthy: failed to connect: context deadline exceeded
https://172.19.104.231:2379 is unhealthy: failed to connect: context deadline exceeded
https://172.19.104.230:2379 is unhealthy: failed to connect: context deadline exceeded
Error: unhealthy cluster
</code></pre>

<p>check etcd member:</p>

<pre><code>[root@iZuf63refzweg1d9dh94t8Z work]# /opt/k8s/bin/etcdctl member list
    56298c42af788da7, started, azshara-k8s02, https://172.19.104.230:2380, https://172.19.104.230:2379
    5ab2d0e431f00a20, started, azshara-k8s01, https://172.19.104.231:2380, https://172.19.104.231:2379
    84c70bf96ccff30f, started, azshara-k8s03, https://172.19.150.82:2380, https://172.19.150.82:2379
</code></pre>

<p>my cluster is deploy success?If not,how to solve the context deadline exceeded error? I tried this:</p>

<pre><code>     export ETCDCTL_API=3
     [root@ops001 ~]# /opt/k8s/bin/etcdctl endpoint status --write-out=table
+----------------+------------------+---------+---------+-----------+-----------+------------+
|    ENDPOINT    |        ID        | VERSION | DB SIZE | IS LEADER | RAFT TERM | RAFT INDEX |
+----------------+------------------+---------+---------+-----------+-----------+------------+
| 127.0.0.1:2379 | 5ab2d0e431f00a20 |  3.3.13 |  2.0 MB |     false |        20 |   39303798 |
+----------------+------------------+---------+---------+-----------+-----------+------------+
[root@ops001 ~]# /opt/k8s/bin/etcdctl endpoint health
127.0.0.1:2379 is healthy: successfully committed proposal: took = 1.816293ms
[root@ops001 ~]# /opt/k8s/bin/etcdctl endpoint health --cluster
https://172.19.150.82:2379 is unhealthy: failed to connect: context deadline exceeded
https://172.19.104.231:2379 is unhealthy: failed to connect: context deadline exceeded
https://172.19.104.230:2379 is unhealthy: failed to connect: context deadline exceeded
Error: unhealthy cluster
</code></pre>

<blockquote>
  <p>how to solve the context deadline exceeded error?</p>
</blockquote>

<p>That error is misleading; it is <em>usually</em> caused by <code>etcdctl</code> not providing credentials and/or not using the same <code>ETCDCTL_API=</code> value as the cluster. If it's a modern <code>etcd</code> version, you'll want <a href="https://github.com/etcd-io/etcd/blob/v3.4.0/Documentation/dev-guide/interacting_v3.md" rel="noreferrer"><code>export ETCDCTL_API=3</code></a>, followed by providing the same <a href="https://github.com/etcd-io/etcd/blob/v3.4.0/Documentation/op-guide/security.md#basic-setup" rel="noreferrer"><code>--cert-file=</code> and <code>--key-file=</code> and likely <code>--trusted-ca-file=</code></a> as was used to start <code>etcd</code> itself.</p>
