HA kubernetes cluster: Accidental kubeadm reset on 1 master node, connection refused when rejoining the cluster
Solution 1:
Figured out what was the issue when I entered ip a
. Realised that ens192 on cp01 still contains the secondary ip address 192.168.1.49.
Simply ip addr del 192.168.1.49/24 dev ens192
and kubeadm join...
and cp01 is able to rejoin the cluster successfully. Can't believe I missed that...