Before kubeadm, city DC techs left swap enabled and control-plane init fails mysteriously. What infrastructure fix aligns with typical kubeadm/kubelet prerequisites?
Select an answer to reveal the explanation.
Short Explanation
Kubernetes nodes like firm ground, not a trampoline of swap. Turn swap off (or follow the supported kubelet config path) before kubeadm init so preflight stops complaining. More swap usually makes the mystery worse, not better.
Full Explanation
kubeadm preflight and kubelet historically expect swap disabled unless the administrator intentionally configures kubelet for swap per current docs. Leaving swap on commonly fails init or produces unstable scheduling behavior. Increasing or network-sharing swap does not satisfy the usual prerequisite. Fix the host configuration, then retry kubeadm.