Merge pull request #76472 from jab-rh/rn-OSDOCS-4969-416

Add release note for changing OVN-Kubernetes internal subnet

Author: jab-rh

release_notes/ocp-4-16-release-notes.adoc

@@ -301,7 +301,6 @@ For further information, see xref:../networking/hardware_networks/configuring-sr
 As of {product-title} 4.16, the SR-IOV Network Operator no longer automatically creates a `SriovOperatorConfig` custom resource (CR). Create the `SriovOperatorConfig` CR using the procedure described in xref:../networking/hardware_networks/configuring-sriov-operator.adoc#nw-sriov-configuring-operator_configuring-sriov-operator[Configuring the SR-IOV Network Operator].
 
 [id="ocp-4-16-q-in-q-support_{context}"]
-[id="ocp-4-16-q-in-q-support"]
 ==== Supporting double-tagged packets (QinQ)
 
 This release introduces 802.1Q-in-802.1Q also known as QinQ support. QinQ introduces a second VLAN tag, where the service provider designates the outer tag for their use, offering them flexibility, while the inner tag remains dedicated to the customer’s VLAN. When two VLAN tags are present in a packet, the outer VLAN tag can be either 802.1Q or 802.1ad. The inner VLAN tag must always be 802.1Q.
@@ -376,6 +375,17 @@ Migration to OVN-Kubernetes is intended to be a one-way process.
 
 For more information, see xref:../networking/ovn_kubernetes_network_provider/migrate-from-openshift-sdn.adoc#nw-ovn-kubernetes-live-migration-about_migrate-from-openshift-sdn[Live migration to the OVN-Kubernetes network plugin overview].
 
+[id="ocp-4-16-networking-changing-ovn-kubernetes-network-plugin-internal-range_{context}"]
+==== Support for changing the OVN-Kubernetes network plugin internal IP address ranges
+
+If you use the OVN-Kubernetes network plugin, you can configure the transit, join, and masquerade subnets. The transit and join subnets can be configured either during cluster installation or after. The masquerade subnet must be configured during installation and cannot be changed after. The subnet defaults are:
+
+- Transit subnet: `100.88.0.0/16` and `fd97::/64`
+- Join subnet: `100.64.0.0/16` and `fd98::/64`
+- Masquerade subnet: `169.254.169.0/29` and `fd69::/125`
+
+For more information about these configuration fields, see xref:../networking/cluster-network-operator.adoc#nw-operator-cr-cno-object_cluster-network-operator[Cluster Network Operator configuration object]. For more information about configuring the transit and join subnets on an existing cluster, see Configure OVN-Kubernetes internal IP address subnets.
+
 [id="ocp-4-16-registry_{context}"]
 === Registry