kubeadm compatibility between "--cri-socket" flag and "init phase" argument kubeadm compatibility between "--cri-socket" flag and "init phase" argument kubernetes kubernetes

kubeadm compatibility between "--cri-socket" flag and "init phase" argument


I see two things that may help:

  1. Check /var/lib/kubelet/kubeadm-flags.env if it is properly configured.

In addition to the flags used when starting the kubelet, the file also contains dynamic parameters such as the cgroup driver and whether to use a different CRI runtime socket (--cri-socket).

More details can be found here.

  1. Check your init config file (kubeadm init --config string will show you the path do the configuration file) and try to add something like this:

apiVersion: kubeadm.k8s.io/v1beta1kind: InitConfigurationnodeRegistration:  criSocket: "unix:///var/run/crio/crio.sock"

Please let me know if that helped.