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

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.

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?

I think I found the isse, the file (on the host) /var/lib/rancher/k3s/agent/etc/cni/net.d/00-multus.conflist contain the wrong path to the kubeconfig:

{
    "cniVersion": "1.0.0",
    "name": "multus-cni-network",
    "plugins": [ {
        "type": "multus",
        "capabilities": {"bandwidth":true,"portMappings":true},
        "logLevel": "verbose",
        "cniConf": "/bitnami/multus-cni/host/etc/cni/net.d",
        "kubeconfig": "/etc/cni/net.d/multus.d/multus.kubeconfig",
        "delegates": [
            {"cniVersion":"1.0.0","name":"cbr0","plugins":[{"delegate":{"forceAddress":true,"hairpinMode":true,"isDefaultGateway":true},"type":"flannel"},{"capabilities":{"portMappings":true},"type":"portmap"},{"capabilities":{"bandwidth":true},"type":"bandwidth"}]}
        ]
    }]
}

The correct path is below cniConf, so it should be: /var/lib/rancher/k3s/agent/etc/cni/net.d/multus.d/multus.kubeconfig

Let's try something, could you try deploying using the args value (so it does not use the default ones) so you can see which exact parameter should be?

I fixed the issue by adding the following arg to args:

--multus-kubeconfig-file-host=/var/lib/rancher/k3s/agent/etc/cni/net.d/multus.d/multus.kubeconfig

This could be set by default from hostCNINetDir, I think?!

Hi,

I'd say so. Would you like to submit a PR adding that parameter?

This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.

This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.

Just to pause the bot, I already added a pull request