Goal

As a Telco operator I'd like to use SR-IOV support described in OSASINFRA-1989 and in OSASINFRA-2193 in deployments configured to use Kuryr-Kubernetes as Kuryr gives superior networking performance over OpenShift-SDN

Problem

The ShiftStack SR-IOV support introduced in 4.7 was not validated on Kuryr deployments. We need to make sure Kuryr itself is okay with VF's coexisting in pod netns. We also need to review UPI instructions regarding SR-IOV and make sure those are valid for Kuryr deployments too.

Also the IPI support planned for 4.8 is not checked for compatibility with Kuryr and we need to make sure any issues are fixes there too.

Why is this important

The primary SR-IOV consumers are Telco operators. For them networking performance (both bandwidth and latency) is an essential metric, so given that in SoS deployments Kuryr-Kubernetes outperforms OpenShift-SDN it is critical to support SR-IOV in them.

Estimate (XS, S, M, L, XL, XXL): S