1. Proposed title of this feature request

Support OVN-K localnet attachment to source-load-balancing bond on default NIC

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

The customer has three main requirements:

• Connect their VMs to a VLAN through a bonding supporting source load balancing
• One of the ports of this bonding is the management interface of the node
• The ports of this bonding vary based on the node, their identity is communicated through PXE

The customer is currently using OpenShift SDN. The solution of their network requirements is the following:

The customer cannot use the same solution with OVN Kubernetes due to the fact that OVN's br-ex is using the default NIC as its port, and therefore it cannot be used by an additional bridge, or reconfigured as an OVS bonding.

The suggested solution is:

• Re-use the first layer of the current solution, let the MCO script of https://github.com/RHsyseng/rhcos-slb/tree/simplify-networking label the primary and secondary NIC with a NetworkManager description
• Once https://issues.redhat.com/browse/OCPBU-453 is implemented, use it to configure an OVS SLB bonding beneath br-ex. This will utilize nmstate policies to "find" previously labeled NIC
• Once https://issues.redhat.com/browse/OCPBU-389 is implemented, use it to define a localnet NetworkAttachmentDefinition, connecting VMs to the physical network under br-ex
• Document and test this solution end-to-end through https://issues.redhat.com/browse/CNV-28007

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

They require the use of OVN Kubernetes for their clusters.

4. List any affected packages or components.

OVN Kubernetes