mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
OCPBUGS-49859: Added br-ex note to the networking route doc
This commit is contained in:
committed by
openshift-cherrypick-robot
parent
0900840ba3
commit
142361d06b
@@ -103,7 +103,7 @@ To define a DNS configuration for a network interface, you must initially specif
|
||||
|
||||
[IMPORTANT]
|
||||
====
|
||||
You cannot use `br-ex` bridge, an OVNKubernetes-managed Open vSwitch bridge, as the interface when configuring DNS resolvers unless you manually configured a customized `br-ex` bridge.
|
||||
You cannot use the `br-ex` bridge, an OVN-Kubernetes-managed Open vSwitch bridge, as the interface when configuring DNS resolvers unless you manually configured a customized `br-ex` bridge.
|
||||
|
||||
For more information, see "Creating a manifest object that includes a customized br-ex bridge" in the _Deploying installer-provisioned clusters on bare metal_ document or the _Installing a user-provisioned cluster on bare metal_ document.
|
||||
====
|
||||
@@ -285,4 +285,11 @@ routes:
|
||||
# ...
|
||||
----
|
||||
<1> The static IP address for the Ethernet interface.
|
||||
<2> Next hop address for the node traffic. This must be in the same subnet as the IP address set for the Ethernet interface.
|
||||
<2> The next hop address for the node traffic. This must be in the same subnet as the IP address set for the Ethernet interface.
|
||||
|
||||
[IMPORTANT]
|
||||
====
|
||||
You cannot use the OVN-Kubernetes `br-ex` bridge as the next hop interface when configuring a static route unless you manually configured a customized `br-ex` bridge.
|
||||
|
||||
For more information, see "Creating a manifest object that includes a customized br-ex bridge" in the _Deploying installer-provisioned clusters on bare metal_ document or the _Installing a user-provisioned cluster on bare metal_ document.
|
||||
====
|
||||
|
||||
Reference in New Issue
Block a user