After the first kubeadm init, a municipal team must expand to additional control-plane nodes. Which join pattern applies?
Select an answer to reveal the explanation.
Short Explanation
Adding another control-plane node is a special VIP join—not a second init ceremony. kubeadm join --control-plane (with the right certs and endpoint) badges the new brain into the existing cluster. A plain worker join won’t install the control-plane stack.
Full Explanation
Expanding an HA control plane uses kubeadm join --control-plane against the existing cluster endpoint, supplying the certificate key and join information kubeadm expects. A second kubeadm init would create a divergent cluster instead of expanding membership. Worker-only joins omit control-plane components.