Running CRI-O with kubeadm
First, CRI-O and
kubeadm reset don't play well together, as
kubeadm reset empties
Therefore, it is good to change the
crio.conf to somewhere kubeadm won't touch.
Further, you'll need to use your plugins to figure out your pod-network-cidr. If you use the default bridge plugin defined here, set
If you're using a flannel network, set
There is a handy, preprepared
/etc/default/kubelet file here
This will configure kubeadm to run with the correct defaults CRI-O needs to run.
Note: This file assumes you've set your cgroup_driver as systemd
Given you've set CIDR, and you've properly set the kubelet file, all you need to do is start crio (as defined here), and run: