The CNI plugins should be installed by the container runtime

[afbjorklund]

Previously, the CNI plugins were installed with Kubernetes (at least since 1.24 and dockershim-magedon)

But they are not required by Kubernetes, which uses the CRI to talk to the runtime that might use CNI...

Currently they are still being installed by default, due to some legacy in the kubernetes release packaging.

But starting with Kubernetes 1.36, that is not true anymore (and it was supposed to be removed in 1.32)

---

For minikube, this means that it is the "provisioner" that installs the plugins and not the "bootstrapper".

That is, the revert of the previous situation (but the status quo is still that they are installed by the OS...)

• Install cri-tools/cni-plugins with bootstrapper, and not with provisioner #15460

The OS only need to provide basic container compatibility, but it should (ideally) not install any runtime.

[afbjorklund]

See this packaging issue, for context. Both the 1.34 and the 1.35 releases were broken, because of this dependency.

• Consider discontinuing the kubernetes-cni package release#4156

---

It is the same CNI binaries, either way. The difference is just a matter of when they are installed in the installation...

• https://github.com/containerd/containerd/blob/main/docs/getting-started.md#step-3-installing-cni-plugins

• https://github.com/cri-o/cri-o/blob/main/install.md#setup-cni-networking

https://github.com/containernetworking/plugins/releases (I don't think that anyone actually installs the cni tool*?)

* https://github.com/containernetworking/cni

Prior to release 0.7.0 the cni release also included a cnitool binary;
as this is a developer tool we suggest you build it yourself.

https://github.com/kubernetes/minikube/tree/master/deploy/iso/minikube-iso/package/cni <- this can be removed