Kubernetes Cluster Downtime Issue After Resetting Old Master Node Following Replacement with New Master Node

[Bangar89]

successfully joined the new master node to the existing Kubernetes cluster and managed to drain and delete the old master node. However, when using the kubeadm reset command to clean the old master node, the cluster goes down.

To join the new master node to the existing cluster, I used the token and certificate key from the old master node.

While installing the control plane components on the new master node, I specified the Load Balancer and initial node IP as the new master node name and updated the Flannel configuration accordingly. Despite these steps, the cluster still goes down after resetting the old master node.

[stmcginnis]

This doesn't sound like a website issue. Is this related to a tutorial you were following on the site?

[sftim]

GitHub is not the right place for support requests.

If you're looking for help, check Server Fault.

You can also post your question on the Kubernetes Slack or the Discuss Kubernetes forum.