By default, the path /etc/cni/multus/net.d is not mounted into the Multus daemon

[ding-9]

What happend:

The default value of the confDir configuration option (/etc/cni/multus/net.d) is not mounted into the Multus daemon when using the installation method:
kubectl apply -f https://raw.githubusercontent.com/k8snetworkplumbingwg/multus-cni/master/deployments/multus-daemonset-thick.yml

What you expected to happen:

The path /etc/cni/multus/net.d should be mounted by default into the Multus daemon

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

• Multus version
  image path and image ID (from 'docker images')
• Kubernetes version (use kubectl version):
• Primary CNI for Kubernetes cluster:
• OS (e.g. from /etc/os-release):
• File of '/etc/cni/net.d/'
• File of '/etc/cni/multus/net.d'
• NetworkAttachment info (use kubectl get net-attach-def -o yaml)
• Target pod yaml info (with annotation, use kubectl get pod <podname> -o yaml)
• Other log outputs (if you use multus logging)

[dougbtv]

I'm wondering why our e2e tests don't pick up on this?

[cyclinder]

Same issue here:

  Warning  FailedCreatePodSandBox  2m37s (x677 over 175m)  kubelet  (combined from similar events): Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "c1f1029bd7058fcce8d5dd71d0c5e976820863eeb10f7905976f408be8f63243": plugin type="multus-shim" name="multus-cni-network" failed (add): CmdAdd (shim): CNI request failed with status 400: 'ContainerID:"c1f1029bd7058fcce8d5dd71d0c5e976820863eeb10f7905976f408be8f63243" Netns:"/var/run/netns/cni-f042fa47-bf1c-1a81-b7b7-f8302b902d7f" IfName:"eth0" Args:"K8S_POD_UID=251c1c0c-730a-4ece-8ea4-c295010f97aa;IgnoreUnknown=1;K8S_POD_NAMESPACE=default;K8S_POD_NAME=test-pod-7b9bdd678f-2h7gc;K8S_POD_INFRA_CONTAINER_ID=c1f1029bd7058fcce8d5dd71d0c5e976820863eeb10f7905976f408be8f63243" Path:"" ERRORED: error configuring pod [default/test-pod-7b9bdd678f-2h7gc] networking: Multus: [default/test-pod-7b9bdd678f-2h7gc/251c1c0c-730a-4ece-8ea4-c295010f97aa]: error loading k8s delegates k8s args: TryLoadPodDelegates: error in getting k8s network for pod: GetNetworkDelegates: failed getting the delegate: GetCNIConfig: err in GetCNIConfigFromFile: No networks found in /etc/cni/multus/net.d
': StdinData: {"capabilities":{"bandwidth":true,"portMappings":true},"clusterNetwork":"/host/etc/cni/net.d/10-calico.conflist","cniVersion":"0.3.1","logLevel":"verbose","logToStderr":true,"name":"multus-cni-network","type":"multus-shim"}

[pasteley]

Same issue here:

This one look like host-run-netns path problem:
https://www.talos.dev/v1.9/kubernetes-guides/network/multus/#configuration

[nirdothan]

How is it supposed to work?
if defaultConfDir= "/etc/cni/multus/net.d" and that hostpath isn't mounted?
The flow is:
CmdAdd()-> LoadNetConf(args.StdinData)-> GetDefaultNetConf(), so unless args.StdinData contains confDir, it will not find anything in that dir.
If that was intentional and users are expected to add their CNI configs to the daemon config, I think that it should at least be documented.