Flannel is broken in Clearlinux due to CNI directory setup in crio.conf about cloud-native-setup HOT 5 CLOSED

/cc @bryteise @hnanni

from cloud-native-setup.

@mcastelino

Hence we should delete crio.conf and restart crio which will automatically setup crio based on latest values.

I'd propose we first check can we get rid of kata-runtime adding a copy of crio.conf in /etc/crio to get to proper stateless. kata-runtime is now installed part of cloud-native-basic so also default crio.conf could assume kata is present. #89 is also relevant in that case.

from cloud-native-setup.

I'd propose we first check can we get rid of kata-runtime adding a copy of crio.conf in /etc/crio to get to proper stateless. kata-runtime is now installed part of cloud-native-basic so also default crio.conf could assume kata is present. #89 is also relevant in that case.

@mythi I agree. It does not hurt to have kata enabled in crio even if the system cannot launch kata (i.e. if VT-x is not enabled or not available). What makes the problem worse was the crio did not seem to output any failure logs. The kata binaries are present and the user may choose to enable VT-x at a later state. Also nothing prevents the user from disabling VT-x. So having kata presetup in the stateless crio.conf makes sense to me.

/cc @krsna1729

from cloud-native-setup.

Tested this with Flannel and Crio, and this works fine. Testing Flannel with containerd, and seems like coredns service isn't starting, debugging it. Shall we add flannel to the CNI as well ? so the user have the option to use Flannel when desired.

from cloud-native-setup.

Closing this as Flannel is merged

from cloud-native-setup.