Feature Overview (aka. Goal Summary)  

For multi-NIC OpenShift deployments, support the use of ovn-kubernetes on non-default host interfaces and split the control data planes across host interfaces.

Goals (aka. expected user outcomes)

Currently, ovn-kubernetes sends all control and data plane traffic over the default (primary) host interface, but customers have strict traffic separation requirements that are best solved by providing support for optionally associating the two types of traffic to a different, non-default host interface.

This feature is not intended to be platorm-specific.

Requirements (aka. Acceptance Criteria):

Use Cases:

Examples:

• one interface for node-to-node VXLAN traffic
• one interface for external traffic

Questions to Answer (Optional):

• What other scrum teams are affected by this optional functionality?

Out of Scope

Background

• Previous R&D work: OCBU-445

Customer Considerations

Documentation Considerations

Interoperability Considerations

• HyperShift support?