kubelet tries to start before crio and fails
On boot, I currently see:
W0524 14:58:00.190342 3182 clientconn.go:1331] [core] grpc: addrConn.createTransport failed to connect to {/var/run/crio/crio.sock /var/run/crio/crio.sock <nil> 0 <nil>}. Err: connection error: desc = "transpor
t: Error while dialing dial unix /var/run/crio/crio.sock: connect: no such file or directory". Reconnecting...
Error: failed to run Kubelet: unable to determine runtime API version: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial unix /var/run/crio/crio.sock: connect: no s
uch file or directory"
kubelet needs to wait for either docker or crio or kubelet should be started under supervision, so it just starts if either of them is around, which is configured.
I wonder what's the smartest way, anyone have an opinion?