openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 21:46:22 +01:00
Code Issues Releases Activity

OCPBUGS-19822 Additional Network and Mettalb cannot use same network

Browse Source
This commit is contained in:
Kevin Quinn
2023-10-10 15:31:01 +01:00
committed by openshift-cherrypick-robot
parent c14f575316
commit 4962dd3602
1 changed files with 7 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
modules/nw-metallb-bgp-limitations.adoc
View File

@@ -18,6 +18,13 @@ However, you can anticipate that a change in the number of `speaker` pods affect
To avoid or reduce the likelihood of a service interruption, you can specify a node selector when you add a BGP peer.
By limiting the number of nodes that start BGP sessions, a fault on a node that does not have a BGP session has no affect on connections to the service.
[id="additional_network_and_metallb_limitation_{context}"]
== Additional Network and MetalLB cannot use same network
There is a limitation when using the same VLAN for both MetalLB and an additional network interface on a source pod. In such cases, a connection failure occurs, when the MetalLB IP and the source pod share the same node.
You can address this by ensuring the MetalLB IP is in another subnet so the traffic coming from a pod would take the default gateway, which is OVN-K and reach the destination via the OVN overlay. Alternatively use a MACVLAN interface instead of a VLAN interface.
[id="nw-metallb-bgp-limitations-single-asn_{context}"]
== Support for a single ASN and a single router ID only