Skip to content

Commit 8771a2f

Browse files
Merge pull request #29318 from sjhala-ccs/BZ-1906354
CNV-BZ-1906354 Added note about OVN Kubernetes related regression in …
2 parents 7dce078 + 671bb09 commit 8771a2f

File tree

1 file changed

+6
-1
lines changed

1 file changed

+6
-1
lines changed

modules/virt-about-nmstate.adoc

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@
33
// * virt/node_network/virt-observing-node-network-state.adoc
44
// * virt/node_network/virt-updating-node-network-config.adoc
55
// * networking/k8s_nmstate/k8s-nmstate-observing-node-network-state.adoc
6-
// * networking/k8s_nmstate/k8s-nmstate-updating-node-network-config.adoc
6+
// * networking/k8s_nmstate/k8s-nmstate-updating-node-network-config.adoc
77

88
[id="virt-about-nmstate_{context}"]
99
= About nmstate
@@ -25,3 +25,8 @@ Node networking is monitored and updated by the following objects:
2525
* Bond
2626

2727
* Ethernet
28+
29+
[NOTE]
30+
====
31+
If your {product-title} cluster uses OVN-Kubernetes as the default Container Network Interface (CNI) provider, you cannot attach a Linux bridge or bonding to the default interface of a host because of a change in the host network topology of OVN-Kubernetes. As a workaround, you can use a secondary network interface connected to your host, or switch to the OpenShift SDN default CNI provider.
32+
====

0 commit comments

Comments
 (0)