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

…-85996-to-enterprise-4.17
openshift · Dec 11, 2024 · f9f7be7 · f9f7be7
2 parents af63fed + e5bfe50
commit f9f7be7
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 1 deletion.
diff --git a/modules/optimizing-mtu-networking.adoc b/modules/optimizing-mtu-networking.adoc
@@ -7,6 +7,6 @@
 
 There are two important maximum transmission units (MTUs): the network interface controller (NIC) MTU and the cluster network MTU.
 
-The NIC MTU is only configured at the time of {product-title} installation. The MTU must be less than or equal to the maximum supported value of the NIC of your network. If you are optimizing for throughput, choose the largest possible value. If you are optimizing for lowest latency, choose a lower value.
+The NIC MTU is configured at the time of {product-title} installation, and you can also change the cluster's MTU as a Day 2 operation. See "Changing cluster network MTU" for more information. The MTU must be less than or equal to the maximum supported value of the NIC of your network. If you are optimizing for throughput, choose the largest possible value. If you are optimizing for lowest latency, choose a lower value.
 
 For OVN and Geneve, the MTU must be less than the NIC MTU by 100 bytes at a minimum.
diff --git a/scalability_and_performance/optimization/optimizing-networking.adoc b/scalability_and_performance/optimization/optimizing-networking.adoc
@@ -25,6 +25,11 @@ Geneve-offload does not reduce latency. However, CPU utilization is reduced even
 
 include::modules/optimizing-mtu-networking.adoc[leveloffset=+1]
 
+[role="_additional-resources"]
+.Additional resources
+
+* xref:../../networking/changing-cluster-network-mtu.adoc#changing-cluster-network-mtu[Changing cluster network MTU]
+
 include::modules/recommended-install-practices.adoc[leveloffset=+1]
 
 include::modules/ipsec-impact-networking.adoc[leveloffset=+1]