OCPBUGS-36674-re: Documented support limitations for day 2 OVNK configs of the primary network

Author: dfitzmau

modules/nw-ovn-kuberentes-limitations.adoc

@@ -3,12 +3,13 @@
 // * networking/ovn_kubernetes_network_provider/about-ovn-kubernetes.adoc
 // * microshift_networking/microshift-nw-ipv6-config.adoc
 
+:_mod-docs-content-type: REFERENCE
 [id="nw-ovn-kubernetes-limitations_{context}"]
 = OVN-Kubernetes IPv6 and dual-stack limitations
 
 The OVN-Kubernetes network plugin has the following limitations:
 
-* If you set the `ipv6.disable` parameter to `1` in the `kernelArgument` section of the `MachineConfig` custom resource (CR) for your cluster, OVN-Kubernetes pods enter a `CrashLoopBackOff` state. Additionally, updating your cluster to a later version of {product-title} fails because the Network Operator is stuck on a `Degraded` state. Red{nbsp}Hat does not support disabling IPv6 adddresses for your cluster so do not set the `ipv6.disable` parameter to `1`.
+* If you set the `ipv6.disable` parameter to `1` in the `kernelArgument` section of the `MachineConfig` custom resource (CR) for your cluster, OVN-Kubernetes pods enter a `CrashLoopBackOff` state. Additionally, updating your cluster to a later version of {product-title} fails because the Network Operator remains on a `Degraded` state. Red{nbsp}Hat does not support disabling IPv6 adddresses for your cluster so do not set the `ipv6.disable` parameter to `1`.
 
 // The foll limitation is also recorded in the installation section.
 ifndef::microshift[]

modules/nw-ovn-kubernetes-features.adoc

@@ -2,6 +2,7 @@
 //
 // * networking/ovn_kubernetes_network_provider/about-ovn-kubernetes.adoc
 
+:_mod-docs-content-type: CONCEPT
 [id="nw-ovn-kubernetes-purpose_{context}"]
 = OVN-Kubernetes purpose
 
@@ -21,3 +22,11 @@ The OVN-Kubernetes network plugin supports the following capabilities:
 * Egress firewall devices and egress IP addresses.
 * Egress router devices that operate in redirect mode.
 * IPsec encryption of intracluster communications.
+
+Red{nbsp}Hat does not support the following postinstallation configurations that use the OVN-Kubernetes network plugin:
+
+* Configuring the primary network interface, including using the NMState Operator to configure bonding for the interface.
+* Configuring a sub-interface or additional network interface on a network device that uses the Open vSwitch (OVS) or OVN-Kubernetes `br-ex` bridge network.
+* Creating additional virtual local area networks (VLANs) on the primary network interface.
+** If you configured the primary network interface for a node as a VLAN during cluster installation, you can create additional VLANs from the base physical interface, such as `eth0.100`. This works because the Open vSwitch (OVS) bridge attaches to the initial VLAN sub-interface, such as `eth0.100`, leaving the base physical interface available for new configurations.
+

networking/ovn_kubernetes_network_provider/about-ovn-kubernetes.adoc

@@ -26,6 +26,7 @@ OVN-Kubernetes runs a daemon on each node. There are daemon sets for the databas
 // OVN-Kubernetes purpose
 include::modules/nw-ovn-kubernetes-features.adoc[leveloffset=+1]
 
+
 // OVN-Kubernetes IPv6 and dual-stack limitations
 include::modules/nw-ovn-kuberentes-limitations.adoc[leveloffset=+1]