Recently I'm trying to deploy Cilium on Kubic and to create k8s manifest
which is using Kubic container images.
Everything is going well except one thing - I'm not sure what to do with
cilium-cni binary (a CNI plugin which needs to be visible by kubelet).
I assumed that since we use (almost) vanilla Kubernetes with kubeadm,
kubelet is going to look for plugins in /opt/cni/bin and that I can just
mount that directory, then copy the binary there from the initContainer
(or as a part of preStart step). But it seems that kubelet is lookng
only at /usr/lib/cni, which is read only and there are only CNI plugins
installed from packages.
I see two potential solutions:
1. Changing the cni-bin-dir parameter for Kubelet to
`/usr/lib/cni,/opt/cni/bin` to support both CNI plugins installed on
host and those installed dynamically.
2. Adding cilium-cni package to patterns-containers.
What do you think?
BTW, I have the manifest here:
It should work if you do `transactional-update pkg install cilium-cni`
and restart nodes before.
To unsubscribe, e-mail: opensuse-kubic+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-kubic+owner(a)opensuse.org