-
Feature Request
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
None
-
Product / Portfolio Work
-
None
-
False
-
-
None
-
None
-
-
None
-
-
None
-
None
-
None
-
None
-
None
1. Proposed title of this feature request
Split OVN-K Cluster Transit Network from Host Machine Network
2. What is the nature and description of the request?
Currently OVN-K is using a Geneve type of encapsulation for Inter Node Transit is using the Host primary IP interface (br-ex over for instance an Infra Bond) to connect other nodes.
That same IP interface used for Host management up to K8S/OCP Cluster Control plane(kubelet) as well.
We would like to separate the Geneve encapsulated inter-node communication IP connectivity form the Host Machine primary network and would like to use an Isolated L2 only network segment (with VLAN tagging) for that purpose.
The VLAN Interface planned to be used for OVN-K Transit network/communication planned to be on a separated NIC/Bond or SR-IOV VF, different from the Primary Host interface.
3. Why does the customer need this? (List the business requirements here)
Customers have strict traffic separation requirements. The ask may be already be tackled by https://issues.redhat.com/browse/OCPSTRAT-544
4. List any affected packages or components.
OVN-K