You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: release_notes/ocp-4-16-release-notes.adoc
+11-1Lines changed: 11 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -167,7 +167,6 @@ For further information, see xref:../networking/hardware_networks/configuring-sr
167
167
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].
168
168
169
169
[id="ocp-4-16-q-in-q-support_{context}"]
170
-
[id="ocp-4-16-q-in-q-support"]
171
170
==== Supporting double-tagged packets (QinQ)
172
171
173
172
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
209
208
210
209
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_.
==== 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.
0 commit comments