MultusDynamicNetworks fails on containerd systems

[KrystianMarek]

What happened:
The addons operator deployed as per instruction
with:

apiVersion: networkaddonsoperator.network.kubevirt.io/v1
kind: NetworkAddonsConfig
metadata:
  name: cluster
spec:
  multus: {}
  multusDynamicNetworks: {}
  linuxBridge: {}
  kubeMacPool: {}
  ovs: {}
  macvtap: {}
  kubeSecondaryDNS: {}
  kubevirtIpamController: {}
  imagePullPolicy: Always

By default deploys multus crio dynamic network controller
Rendering the controller broken when deployed on a system with containerd. There is another manifest dedicated to containerd systems this. NetworkAddonsConfig.spec.multusDynamicNetworks does not allow any configuration, not even choosing the correct manifest.

What you expected to happen:
multusDynamicNetworks works on systems with containerd

How to reproduce it (as minimally and precisely as possible):
Deploy NetworkAddonsConfig mentioned above on a system with containerd, for example ubuntu.

Workaround:
Disable multusDynamicNetworks by deploying

apiVersion: networkaddonsoperator.network.kubevirt.io/v1
kind: NetworkAddonsConfig
metadata:
  name: cluster
spec:
  imagePullPolicy: IfNotPresent
  kubeMacPool: {}
  kubeSecondaryDNS: {}
  kubevirtIpamController: {}
  linuxBridge: {}
  macvtap: {}
  multus: {}
  ovs: {}

Deploy dynamic-networks-controller separately. Be mindful of namespaces. Cluster network addons operator deploys to cluster-network-addons namespace.

Environment:

• KubeVirt version (use virtctl version): 1.3.0
• Kubernetes version (use kubectl version): v1.28.6
• VM or VMI specifications: N/A
• Cloud provider or hardware configuration: bare metal
• OS (e.g. from /etc/os-release): ubuntu
• Kernel (e.g. uname -a): N/A
• Install tools: N/A
• Others: N/A

[maiqueb]

/cc

[oshoval]

maybe this one suggests the solution #1804 ?

[kubevirt-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[kubevirt-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

[kubevirt-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

[kubevirt-bot]

@kubevirt-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.