[Bug 1214406] [kubeadm1.27] Multiple Issues before `kubeadm init` runs successfully

https://bugzilla.suse.com/show_bug.cgi?id=1214406 https://bugzilla.suse.com/show_bug.cgi?id=1214406#c1 --- Comment #1 from Egbert Eich <eich@suse.com> --- I was partly wrong with my assessment in item 1. in above description: It is perfectly fine to use crio runtime - however, it needs to be enabled and running at the time `kubeadm init` runs. Thus, this should be set in a postinstall script. NOTE: before doing so it should be checked if another container runtime (containerd) is already enabled (or even running). It it is running, nothing should be done (ie crio should not be touched). If it is just enabled, it should be started. -- You are receiving this mail because: You are on the CC list for the bug.