Skip to content

Commit 24bc60d

Browse files
committed
Add release note for changing OVN-Kubernetes internal subnet
- https://issues.redhat.com/browse/OSDOCS-4969 - https://issues.redhat.com/browse/SDN-3516
1 parent efaa432 commit 24bc60d

File tree

1 file changed

+11
-1
lines changed

1 file changed

+11
-1
lines changed

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

Lines changed: 11 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -167,7 +167,6 @@ For further information, see xref:../networking/hardware_networks/configuring-sr
167167
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].
168168

169169
[id="ocp-4-16-q-in-q-support_{context}"]
170-
[id="ocp-4-16-q-in-q-support"]
171170
==== Supporting double-tagged packets (QinQ)
172171

173172
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.
@@ -209,6 +208,17 @@ If you have already upgraded your cluster to {product-title} {product-version} a
209208

210209
For more information, see xref:../networking/ovn_kubernetes_network_provider/converting-to-dual-stack.html#nw-dual-stack-convert_converting-to-dual-stack[Converting to a dual-stack cluster network] in _Converting to IPv4/IPv6 dual-stack networking_.
211210

211+
[id="ocp-4-16-networking-changing-ovn-kubernetes-network-plugin-internal-range_{context}"]
212+
==== Support for changing the OVN-Kubernetes network plugin internal IP address ranges
213+
214+
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:
215+
216+
- Transit subnet: `100.88.0.0/16` and `fd97::/64`
217+
- Join subnet: `100.64.0.0/16` and `fd98::/64`
218+
- Masquerade subnet: `169.254.169.0/29` and `fd69::/125`
219+
220+
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.
221+
212222
[id="ocp-4-16-registry_{context}"]
213223
=== Registry
214224

0 commit comments

Comments
 (0)