Seeing CNI error for master kubelet, does it matter?

[Arve Knudsen]

Hey

I'm trying to implement Tectonic Installer on DigitalOcean, and while I used to have a working port, it's not functioning after I re-aligned it with Tectonic Installer upstream at some point.

It seems the master kubelet isn't functioning properly while trying to bootstrap the Kubernetes control plane. I'm not sure what is the problem exactly, but I keep seeing an error message about being unable to initialize the network plugin. Can someone tell me if this is a real error, or just a warning that I should ignore?

Oct 29 14:20:27 coreos-testing-master-0 kubelet-wrapper[725]: W1029 14:20:27.954258     725 cni.go:189] Unable to update cni config: No networks found in /etc/kubernetes/cni/net.d

Oct 29 14:20:27 coreos-testing-master-0 kubelet-wrapper[725]: E1029 14:20:27.955556     725 kubelet.go:2141] Container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:docker: network plugin is not ready: cni config uninitialized

Thanks,

Arve