minikube fails to start w/ none driver and K8s v1.24+ w/o containernetworking-plugins

[spowelljr]

If containernetworking-plugins are not installed (/opt/cni/bin is empty) starting minikube with the none driver and Kubernetes v1.24+, CoreDNS and storage-provisioner pods fail to run.

If the --wait=all flag is not passed it will appear to succeed, but if you check kubectl pods -A you'll see the coredns and storage-provisioner pods will never come up.

NAMESPACE     NAME                                        READY   STATUS    RESTARTS   AGE
kube-system   coredns-787d4945fb-74xcd                    0/1     Pending   0          8s
kube-system   etcd-ubuntu-20-agent-2                      1/1     Running   2          22s
kube-system   kube-apiserver-ubuntu-20-agent-2            1/1     Running   2          23s
kube-system   kube-controller-manager-ubuntu-20-agent-2   1/1     Running   2          23s
kube-system   kube-proxy-7x2k9                            1/1     Running   0          9s
kube-system   kube-scheduler-ubuntu-20-agent-2            1/1     Running   2          23s
kube-system   storage-provisioner                         0/1     Pending   0          7s

If you pass --wait=all the start will fail after waiting 6 minutes for the above pods to start.

This stems from cri-docker failing due to the missing plugins:

cri-dockerd[11762]: time="2023-04-25T13:11:31Z" level=error msg="Error validating CNI config list (\n{\n  \"cniVersion\": \"0.3.1\",\n  \"name\": \"bridge\",\n  \"plugins\": [\n    {\n      \"type\": \"bridge\",\n      \"bridge\": \"bridge\",\n      \"addIf\": \"true\",\n      \"isDefaultGateway\": true,\n      \"forceAddress\": false,\n      \"ipMasq\": true,\n      \"hairpinMode\": true,\n      \"ipam\": {\n          \"type\": \"host-local\",\n          \"subnet\": \"10.244.0.0/16\"\n      }\n    },\n    {\n      \"type\": \"portmap\",\n      \"capabilities\": {\n          \"portMappings\": true\n      }\n    }\n  ]\n}\n): [failed to find plugin \"bridge\" in path [/opt/cni/bin] failed to find plugin \"portmap\" in path [/opt/cni/bin]]"

Resulting in kubelet failing:

kubelet[13276]: E0425 13:11:28.362943   13276 kubelet.go:2475] "Container runtime network not ready" networkReady="NetworkReady=false reason:NetworkPluginNotReady message:docker: network plugin is not ready: cni config uninitialized"

Ideally we would install this for the user as per #15460

But for now the following three actions should be completed:

• Update none driver docs to state containernetworking-plugins are required (site: add containernetworking-plugins to none driver docs #16379)
• Check for the existence of containernetworking-plugins and notify the user if it's not installed (none driver: check for CNI plugins #16419)
• Add install script to install containernetworking-plugins and add it to none driver integration tests (CI: install cni-plugins for none driver tests #16380)