http://bugzilla.opensuse.org/show_bug.cgi?id=1093132
http://bugzilla.opensuse.org/show_bug.cgi?id=1093132#c8
--- Comment #8 from Panagiotis Georgiadis
The kubelet is now restarting every few seconds, as it waits in a crashloop for kubeadm to tell it what to do. This crashloop is expected and normal, please proceed with the next step and the kubelet will start running normally.
So I guess that kubeadm expects kubelet to be already running before issuing 'kubeadm init'. In that case we have a bug with that port that is being used. However, googling for that most people say that 'kubeadm reset' fixing that problem with the port. Doing so, one of the steps is to stop kubelet:
[reset] Stopping the kubelet service.
And as soon as the kubelet is stopped, I end up with the CRI-ERROR. To sum up: ---------- kubelet running: Port error kubelet not running: CRI error Seems I'm stuck :/ -- You are receiving this mail because: You are on the CC list for the bug.