A city SRE accidentally runs kubeadm init a second time on a node that still has leftover cluster state from a prior attempt. What should they do before a clean re-initialization?
Select an answer to reveal the explanation.
Short Explanation
Trying to init twice on a dirty node is like pouring a new foundation over rubble—you’re asking for cracks. Reset the node first (kubeadm reset, plus any leftover CNI/iptables mess), then init on a clean slate. Skipping reset is how you get half-dead certificates and confused etcd directories.
Full Explanation
kubeadm init expects a node without an existing cluster bootstrap. kubeadm reset removes kubeadm-managed local state so a subsequent init can create fresh certificates, static pods, and etcd data. Partial cleanup such as deleting only manifests leaves conflicting PKI or etcd directories that break the new control plane.