Merge pull request #92611 from dfitzmau/OSDOCS-8326-14

[enterprise-4.14] OSDOCS-8326: Removed value cannot be changed DAY 2 from SDN table

Author: dfitzmau

modules/nw-operator-cr.adoc

@@ -29,13 +29,6 @@ ifeval::["{context}" == "cluster-network-operator"]
 :operator:
 endif::[]
 
-ifeval::["{context}" == "post-install-network-configuration"]
-:post-install-network-configuration:
-endif::[]
-ifeval::["{context}" == "installing-ibm-cloud-network-customizations"]
-:ibm-cloud:
-endif::[]
-
 :_mod-docs-content-type: CONCEPT
 [id="nw-operator-cr_{context}"]
 = Cluster Network Operator configuration
@@ -49,13 +42,13 @@ The CNO configuration inherits the following fields during cluster installation
 `defaultNetwork.type`:: Cluster network plugin, such as OpenShift SDN or OVN-Kubernetes.
 
 // For the post installation assembly, no further content is provided.
-ifdef::post-install-network-configuration,operator[]
+ifdef::operator[]
 [NOTE]
 ====
 After cluster installation, you can only modify the `clusterNetwork` IP address range. The default network type can only be changed from OpenShift SDN to OVN-Kubernetes through migration.
 ====
 endif::[]
-ifndef::post-install-network-configuration[]
+
 You can specify the cluster network plugin configuration for your cluster by setting the fields for the `defaultNetwork` object in the CNO object named `cluster`.
 
 [id="nw-operator-cr-cno-object_{context}"]
@@ -182,9 +175,9 @@ The maximum transmission unit (MTU) for the VXLAN overlay network. This is detec
 
 If the auto-detected value is not what you expect it to be, confirm that the MTU on the primary network interface on your nodes is correct. You cannot use this option to change the MTU value of the primary network interface on the nodes.
 
-If your cluster requires different MTU values for different nodes, you must set this value to `50` less than the lowest MTU value in your cluster. For example, if some nodes in your cluster have an MTU of `9001`, and some have an MTU of `1500`, you must set this value to `1450`.
+If your cluster requires different MTU values for different nodes, you must set this value to `50` less than the lowest MTU value in your cluster. For example, if some nodes in your cluster have an MTU of `9001`, and some have an MTU of `1500`, you must set this value to `1450`. 
 
-This value cannot be changed after cluster installation.
+You can set the value during cluster installation or as a post-installation task. For more information, see "Changing the MTU for the cluster network" in the {product-title} Networking document. 
 endif::operator[]
 ifdef::operator[]
 The maximum transmission unit (MTU) for the VXLAN overlay network. This value is normally configured automatically.
@@ -206,6 +199,7 @@ endif::operator[]
 
 |====
 
+ifdef::operator[]
 .Example OpenShift SDN configuration
 [source,yaml]
 ----
@@ -216,6 +210,7 @@ defaultNetwork:
     mtu: 1450
     vxlanPort: 4789
 ----
+endif::operator[]
 
 [discrete]
 [id="nw-operator-configuration-parameters-for-ovn-sdn_{context}"]
@@ -365,6 +360,7 @@ One of the following additional audit log targets:
 // end::policy-audit[]
 
 [id="gatewayConfig-object_{context}"]
+
 .`gatewayConfig` object
 [cols=".^2,.^2,.^6a",options="header"]
 |====
@@ -497,15 +493,8 @@ spec:
 
 ----
 endif::operator[]
-endif::post-install-network-configuration[]
 
 ifeval::["{context}" == "cluster-network-operator"]
 :!operator:
 endif::[]
 
-ifeval::["{context}" == "post-install-network-configuration"]
-:!post-install-network-configuration:
-endif::[]
-ifeval::["{context}" == "installing-ibm-cloud-network-customizations"]
-:!ibm-cloud:
-endif::[]