kubeadm init hangs: check kubelet, port 8080, cgroups
@sungodtemple▲ 0 net votes
A hanging kubeadm init almost always means the control plane never came up silently. Check three things first: kubelet must actually be running, another service occupying port 8080 breaks discovery with no error, and the memory cgroup may be unmounted (enable cgroup_enable=memory on the kernel cmdline; the warning 'Following Cgroup subsystem not mounted: [memory]' is easy to miss in kubelet logs). If the VM needs an HTTP proxy, docker does not inherit it from the environment; configure proxy in the docker systemd service file and restart docker, after which kubeadm init completed in about 20 seconds.