What happend:
After node reboot multus doesn't call the ovs CNI to create the interface in a VM created by kubevirt
What you expected to happen:
Interface to be created
How to reproduce it (as minimally and precisely as possible):
Reboot the node
Anything else we need to know?:
I installed multus using the cluster network addons. After restarting the multus pods everything started working again.
The network addons config file:
Environment:
kubeadm 1.31, ubuntu 24.04, cilium is the primary CNI
Multus version
image path and image ID (from 'docker images') ghcr.io/k8snetworkplumbingwg/multus-cni@sha256:c8bfe5bad3b5371a5677feb9e8e162da91b61bcac409c244f6f1b18c801ad006
Kubernetes version (use kubectl version):
Client Version: v1.30.2
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.31.3
What happend: After node reboot multus doesn't call the ovs CNI to create the interface in a VM created by kubevirt
What you expected to happen: Interface to be created
How to reproduce it (as minimally and precisely as possible): Reboot the node
Anything else we need to know?: I installed multus using the cluster network addons. After restarting the multus pods everything started working again. The network addons config file:
Environment: kubeadm 1.31, ubuntu 24.04, cilium is the primary CNI
Multus version image path and image ID (from 'docker images')
ghcr.io/k8snetworkplumbingwg/multus-cni@sha256:c8bfe5bad3b5371a5677feb9e8e162da91b61bcac409c244f6f1b18c801ad006
Kubernetes version (use
kubectl version
):Primary CNI for Kubernetes cluster: Cilium
OS (e.g. from /etc/os-release):
File of '/etc/cni/net.d/'
File of '/etc/cni/multus/net.d': Non existent
NetworkAttachment info (use
kubectl get net-attach-def -o yaml
)apiVersion: k8s.cni.cncf.io/v1 kind: NetworkAttachmentDefinition metadata: annotations: kubectl.kubernetes.io/last-applied-configuration: | {"apiVersion":"k8s.cni.cncf.io/v1","kind":"NetworkAttachmentDefinition","metadata":{"annotations":{},"name":"kube-test","namespace":"virtual-machines"},"spec":{"config":"{\n \"cniVersion\": \"0.3.1\",\n \"type\": \"ovs\",\n \"bridge\": \"br0\",\n \"vlan\": 11\n}\n"}} creationTimestamp: "2024-11-22T05:44:45Z" generation: 2 name: kube-test namespace: virtual-machines resourceVersion: "1025311" uid: 36992f9b-7e88-47ff-813d-1c8cc20536a9 spec: config: | { "cniVersion": "0.4.0", "type": "ovs", "bridge": "br0", "vlan": 11 } kind: List metadata: resourceVersion: ""
Target pod yaml info (with annotation, use
kubectl get pod <podname> -o yaml
)Other log outputs (if you use multus logging) Multus logs:
Container statuses of VM: