[bitnami/multus-cni] failed to get context for the kubeconfig

[brightdroid]

Name and Version

bitnamicharts/multus-cni:2.1.19

What architecture are you using?

amd64

What steps will reproduce the bug?

• installed k3s v1.29.10+k3s1
• installed multus with below values
• start netshot debug pod: kubectl netshoot run tmp-shell
• inspect pod "tmp-shell" (which did not start)

Are you using any custom parameters or values?

fullnameOverride: multus
hostCNIBinDir: /var/lib/rancher/k3s/data/cni/
hostCNINetDir: /var/lib/rancher/k3s/agent/etc/cni/net.d

What is the expected behavior?

No response

What do you see instead?

Logs from "tmp-shell" pod
Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "3574ecbded3a47def3133b1d8a783035a1a63f6d95ba4c4a3845c5cf24c78614": plugin type="multus" failed (add): Multus: error getting k8s client: GetK8sClient: failed to get context for the kubeconfig /etc/cni/net.d/multus.d/multus.kubeconfig: stat /etc/cni/net.d/multus.d/multus.kubeconfig: no such file or directory

Additional information

Logs from multus pod:

multus-wwvcj multus-cni kubeconfig is created in /bitnami/multus-cni/host/etc/cni/net.d/multus.d/multus.kubeconfig                                                                                                                                           
multus-wwvcj multus-cni kubeconfig file is created.                                                                                                                                                                                                          
multus-wwvcj multus-cni master capabilities is get from conflist                                                                                                                                                                                             
multus-wwvcj multus-cni multus config file is created.                                                                                                                                                                                                       
multus-wwvcj generate-kubeconfig multus multus copy succeeded!                                                                                                                                                                                               

[javsalgar]

Hi,

This is strange, because looking at the logs the kubeconfig should be there. Could you try entering the container with kubectl exec and verify that it created the kubeconfig file? If so, maybe the hostCNINetDir is incorrect

[brightdroid]

I think the multus daemonset use the wrong paths.

• the multus pods created the kubeconfig on the hosts in /var/lib/rancher/k3s/agent/etc/cni/net.d/multus.d/multus.kubeconfig (as expected)
• the multus pods have the host path /var/lib/rancher/k3s/agent/etc/cni/net.d mounted at /bitnami/multus-cni/host/etc/cni/net.d

So the multus pods should use the path /bitnami/multus-cni/host/etc/cni/net.d/multus.d/multus.kubeconfig.

[javsalgar]

Could you try changing the path in the YAML to confirm this? If so, as you spotted the issue, would you like to submit a PR?