# Cluster failed when I want add a new master node to cluster with kubeadm

**URL:** <https://discuss.kubernetes.io/t/cluster-failed-when-i-want-add-a-new-master-node-to-cluster-with-kubeadm/14319>\
**Category:** General Discussions\
**Created:** [December 31, 2020, 7:54pm UTC](https://discuss.kubernetes.io/t/cluster-failed-when-i-want-add-a-new-master-node-to-cluster-with-kubeadm/14319 "2020-12-31T19:54:39Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![falahatiali](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/falahatiali/32/6611_2.png) [@falahatiali](https://discuss.kubernetes.io/u/falahatiali)\
**Post date:** [December 31, 2020, 7:54pm UTC](https://discuss.kubernetes.io/t/cluster-failed-when-i-want-add-a-new-master-node-to-cluster-with-kubeadm/14319/1 "2020-12-31T19:54:39Z")

</div>

Asking for help? Comment out what you need so we can get more information to help you!

### Cluster information:

Kubernetes version:  
Cloud being used: (put bare-metal if not on a public cloud)  
Installation method: Kubeadm  
Host OS: ubuntu 20.04  
CNI and version: calico 3.17  
CRI and version: docker 20

I have a master node and cluster is healthy but when I want to add a new master node with this command

```auto
kubeadm join 194.5.207.152:8443 --token 6blql0.yt17i59h9b30ilnb --discovery-token-ca-cert-hash sha256:d6b3da92afd7b74919bbcf7a902d1a1f9ec325af664223de720cf7f5d6224407 --control-plane --certificate-key 17777d59ffc5d5dfdb5defdaca8899456b6511d5b87008d1a760f5b25f90d0aa

```

it gives me following error  
[kubelet-start] Waiting for the kubelet to perform the TLS Bootstrap…  
[etcd] Announced new etcd member joining to the existing etcd cluster  
[etcd] Creating static Pod manifest for “etcd”  
[etcd] Waiting for the new etcd member to join the cluster. This can take up to 40s  
[kubelet-check] Initial timeout of 40s passed.

and also master1 fails. what should I do for solving this unknown problem

You can format your yaml by highlighting it and pressing Ctrl-Shift-C, it will make your output easier to read.

---

<div class="post-metadata">

**Author:** ![ThePieMonster](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/thepiemonster/32/6657_2.png) [@ThePieMonster](https://discuss.kubernetes.io/u/ThePieMonster)\
**Post date:** [January 12, 2021, 8:02pm UTC](https://discuss.kubernetes.io/t/cluster-failed-when-i-want-add-a-new-master-node-to-cluster-with-kubeadm/14319/2 "2021-01-12T20:02:34Z")

</div>

Is your issue like this post perhaps?  
[Kubernetes - kubeadm join - Connection refused after new control plane joined](https://serverfault.com/questions/1049590/kubernetes-kubeadm-join-connection-refused-after-new-control-plane-joined)

---

<div class="post-metadata">

**Author:** ![anch2150](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/anch2150/32/7159_2.png) [@anch2150](https://discuss.kubernetes.io/u/anch2150)\
**Post date:** [March 12, 2021, 10:50am UTC](https://discuss.kubernetes.io/t/cluster-failed-when-i-want-add-a-new-master-node-to-cluster-with-kubeadm/14319/3 "2021-03-12T10:50:28Z")

</div>

I had the same issue. I’m running `kubernetes 1.20.4` on `Raspberry Pi 4, Ubuntu 20.04`

```bash
kubeadm init ...
kubectl apply -f calico.yaml

```

on the first node completed without any error.

As long as I join a second control plane node, the first also dies after

```auto
...
[kubelet-start] Waiting for the kubelet to perform the TLS Bootstrap...
[etcd] Announced new etcd member joining to the existing etcd cluster
[etcd] Creating static Pod manifest for "etcd"
[etcd] Waiting for the new etcd member to join the cluster. This can take up to 40s
[kubelet-check] Initial timeout of 40s passed.

```