1. Proposed title of this feature request

Using user provided NetworkAttachmentDefinition with SR-IOV Operator.

2. What is the nature and description of the request?

The OpenShift documentation recommends configuring SR-IOV network attachments through the SriovNetwork CR which triggers the creation of the required NetworkAttachmentDefinition CR automatically.

Some partners/customers are not using SriovNetwork CRs to drive SR-IOV network attachments and are instead applying user (partner/customer) generated NetworkAttachmentDefinition CRs directly.

Currently adding additional networks using a NetworkAttachmentDefinition CR is tested as part of the Cluster Network Operator but it is not tested in combination with the SR-IOV Operator.

3. Why does the customer need this? (List the business requirements here)

Some partners/customers are already doing this (because functionally it works) and the reasons cited why they could not change to using SriovNetwork CRs instead were:

• Some 3rd party CaaS do not use the SR-IOV Operator, and they need to fall back to using NetworkAttachmentDefinition CRs and they would like to avoid maintaining two sets of configuration.
• SriovNetwork CRs need to be created in namespace openshift-sriov-network-operator, resulting in the need for additional/more complex RBAC configuration.

4. List any affected packages or components.

SR-IOV Operator