Merge pull request #86857 from openshift-cherrypick-robot/cherry-pick…

…-86777-to-enterprise-4.12

[enterprise-4.12] OCPBUGS#47532: Added note to the nw-operator-cr file

modules/nw-network-config.adoc

@@ -37,6 +37,6 @@ Set the `networking.machineNetwork` to match the CIDR that the preferred NIC res
 The CIDR range `172.17.0.0/16` is reserved by libVirt. You cannot use this range or any range that overlaps with this range for any networks in your cluster.
 ====
 
-Phase 2:: After creating the manifest files by running `openshift-install create manifests`, you can define a customized Cluster Network Operator manifest with only the fields you want to modify. You can use the manifest to specify advanced network configuration.
+Phase 2:: After creating the manifest files by running `openshift-install create manifests`, you can define a customized Cluster Network Operator manifest with only the fields you want to modify. You can use the manifest to specify an advanced network configuration.
 
 You cannot override the values specified in phase 1 in the `install-config.yaml` file during phase 2. However, you can further customize the network plugin during phase 2.

modules/nw-operator-cr.adoc

@@ -126,6 +126,11 @@ If you are using the OVN-Kubernetes cluster network plugin, the kube-proxy confi
 
 |====
 
+[IMPORTANT]
+====
+For a cluster that needs to deploy objects across multiple networks, ensure that you specify the same value for the `clusterNetwork.hostPrefix` parameter for each network type that is defined in the `install-config.yaml` file. Setting a different value for each `clusterNetwork.hostPrefix` parameter can impact the OVN-Kubernetes network plugin, where the plugin cannot effectively route object traffic among different nodes.
+====
+
 [discrete]
 [id="nw-operator-cr-defaultnetwork_{context}"]
 === defaultNetwork object configuration