After install collection with cri-o kubelet not start

[aleksey005]

After install collection kubelet not start with error socket connection, testing playbook for Ubuntu 22.04 and Debian 12.
Playbook configured Kubelet default use containerd socket not cri-o socket.
To configure it correctly, you have to skip the Kubernetes installation option and issue the command manually
kubeadm init
--pod-network-cidr=10.244.0.0/16
--upload-certs
--cri-socket=unix:/var/run/crio/crio.sock
--control-plane-endpoint=192.168.100.100

in role --cri-socket=unix:///var/run/crio/crio.sock and apparently this switches kubelet to use the default containerd socket

[hswong3i]

I just found CI failed, too

https://gitlab.com/alvistack/ansible-collection-atlassian/-/pipelines/1154503981

Will check that now, thank you very much for bug reporting 🙏