The K3s CNI binaries are installed alongside the rest of the bundled userspace, and the managed containerd config is updated on restart to point at the current bin dir under /var/lib/rancher/k3s/data/XXX/bin. This makes it difficult to install custom CNI plugins, as the path used by ...
We added a static CNI bin dir in#10868, but that directory cannot be used in the K3s docker image because the CNI bins in the docker image are just in /bin: root@k3s-server-1:~#grep -C1 bin_dir /var/lib/rancher/k3s/agent/etc/containerd/config.toml[plugins."io.containerd.grpc.v1....
└─6504 /usr/bin/kubelet --bootstrap-kubeconfig=/etc/kubernetes/bootstrap-kubelet.conf --kubeconfig=/etc/kubernetes/kubelet.conf --config=/var/lib/kubelet/config.yaml --cgroup-driver=cgroupfs --cni-bin-dir=/opt/cni/bin --cni-conf-dir=/etc/cni/net.d --network-plugin=cni --cni-bin-...
Backport fix for CNI bin dir changes with K3s version CNI bin dir changes with K3s version #10869 brandond self-assigned this Sep 23, 2024 Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment ...
Backport fix for CNI bin dir changes with K3s version CNI bin dir changes with K3s version #10869 brandond self-assigned this Sep 23, 2024 Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment ...
Backport fix for CNI bin dir changes with K3s version CNI bin dir changes with K3s version #10869 brandond self-assigned this Sep 23, 2024 Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment ...
Backport fix for CNI bin dir changes with K3s version CNI bin dir changes with K3s version #10869 brandond self-assigned this Sep 23, 2024 Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment ...
I still think we should completely remove the autodetect and always respect cniBinDir (as set either explicitly or by the gke platform profile), not only is that Helm field deprecated but given what you said above, the autodetection is known-broken even in GKE. And if you install on gke...