search

k8snetworkplumbingwg / sriov-cni

DPDK & SR-IOV CNI plugin
Apache License 2.0
309 stars 146 forks source link

Allow to rename VF in container when using DHCP IPAM and Multus #41

Closed Mmduh-483 closed 5 years ago

Mmduh-483 commented 5 years ago

By changing the _CNIIFNAME enviroment variable to the VF's new name to support using intel-multus with renaming interface, when multus move the interface to the container it will name the first VF eth0 and then follow the pattern of netX where X start from 0, so when the interface moved with sriov-cni name mutlus will not find the interface with the name it set

zshi-redhat commented 5 years ago

This looks like a problem of Multus which doesn't respect the CNI_IFNAME when release/delete the interface. For SRIOV CNI, it receives the pod interface name passing from Multus unless the if0name is set in SRIOV net-attach-def custom resource.