-
Epic
-
Resolution: Unresolved
-
Normal
-
None
-
Expose MTU for vfio-pci SR-IOV devices to Pod
-
5
-
False
-
-
False
-
Not Selected
-
To Do
-
TELCOSTRAT-43 - SR-IOV sub features
-
Developer Preview
Epic Goal
- This epic is to track the review effort required for the CNF epic: https://issues.redhat.com/browse/CNF-7665
Notes
- For kernel bound SR-IOV interfaces, the MTU is set on the VF netdevice. But there is no such device in case of vfio-pci, and each and every vfio-user need to define its own pod env variable or file. This can be done by the CNF Operator, helm chart, ... and there is no way to ensure that this MTU correspond to the MTU defined in SriovNetworkNodePolicy
- sscheink@redhat.com proposed implementation: "
I think the solution for this will be to pass the information in the device Info annotation that we already add to the pod.
We will need to extend the https://github.com/k8snetworkplumbingwg/device-info-spec to allow the exposure of MTU for network devices
