<p>I have a single node kubernetes cluster running. Everything working fine, but when I run the "kubectl get cs" (kubectl get componentstatus) it showing two instance of etcd. I have running a single etcd instance.</p>

<p><code>[root@master01 vagrant]# kubectl get cs
NAME                 STATUS    MESSAGE              ERROR
controller-manager   Healthy   ok
scheduler            Healthy   ok
etcd-0               Healthy   {"health": "true"}
etcd-1               Healthy   {"health": "true"}</code></p>

<p><code>[root@master01 vagrant]# etcdctl member list
19ef3eced66f4ae3: name=master01 peerURLs=http://10.0.0.10:2380 clientURLs=http://0.0.0.0:2379 isLeader=true</code></p>

<p><code>[root@master01 vagrant]# etcdctl cluster-health
member 19ef3eced66f4ae3 is healthy: got healthy result from http://0.0.0.0:2379
cluster is healthy</code></p>

<p>Etcd is running as a docker container. In the /etc/systemd/system/etcd.service file single etcd cluster is mentioned.(<a href="http://10.0.0.10:2380" rel="nofollow noreferrer">http://10.0.0.10:2380</a>)</p>

<p><code>/usr/local/bin/etcd \
    --name master01 \
    --data-dir /etcd-data \
    --listen-client-urls http://0.0.0.0:2379 \
    --advertise-client-urls http://0.0.0.0:2379 \
    --listen-peer-urls http://0.0.0.0:2380 \
    --initial-advertise-peer-urls http://10.0.0.10:2380 \
    --initial-cluster master01=http://10.0.0.10:2380 \
    --initial-cluster-token my-token \
    --initial-cluster-state new \</code></p>

<p>Also in the api server config file /etc/kubernetes/manifests/api-srv.yaml --etcd-servers flag is used.</p>

<p><code>- --etcd-servers=http://10.0.0.10:2379,</code></p>

<p><code>[root@master01 manifests]# netstat -ntulp |grep etcd
tcp6       0      0 :::2379                 :::*                    LISTEN      31109/etcd
tcp6       0      0 :::2380                 :::*                    LISTEN      31109/etcd</code></p>

<p>Any one know why it showing etcd-0 and etcd-1 in "kubectl get cs" ?. Any help is appreciated.</p>

Jyothish
<p>Despite the fact that @Jyothish Kumar S has found the root cause on his own and fixed the issue - It's a good practice to have an answer that will be available for those, who will face the same problem in the future.</p>

<p>Issue came from missconfiguration in API server config file <code>/etc/kubernetes/manifests/api-srv.yaml</code> where<code>--etcd-servers</code>  was set in an inappropriate way. 
All flags for <code>kube-apiserver</code> along with their descriptions may be found <a href="https://kubernetes.io/docs/reference/command-line-tools-reference/kube-apiserver/" rel="nofollow noreferrer">here</a>.
So, the issue was in the last comma in <code>--etcd-servers=http://10.0.0.10:2379,</code> line. This comma was interpreted as new ETCD server record <code>http://:::2379</code> and that’s why in the <code>"kubectl get cs"</code> output we were able to see two etcd records instead of one.
Pay attention to this aspect while configuring etcd.</p>
