openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 21:46:22 +01:00
Code Issues Releases Activity

Merge pull request #54052 from ahardin-rh/sdn-deprecation

Browse Source 
Added SDN support notes + noted performance improvements
This commit is contained in:
Ashley Hardin
2023-01-10 13:32:16 -05:00
committed by GitHub
parent c510737aab 6a113dcc42
commit bb37dfffb6
1 changed files with 12 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
release_notes/ocp-4-12-release-notes.adoc
View File

@@ -156,7 +156,7 @@ With this release, there are several updates to the *Administrator* perspective
* The {product-title} web console displays a `ConsoleNotification` if the cluster is upgrading. Once the upgrade is done, the notification is removed.
* A *_restart rollout_* option for the `Deployment` resource and a *_retry rollouts_* option for the `DeploymentConfig` resource are available on the *Action* and *Kebab* menus.
* You can view a list of supported clusters on the *All Clusters* dropdown list. The supported clusters include {product-title}, {product-title} Service on AWS (ROSA), Azure Red Hat OpenShift (ARO), ROKS, and {product-dedicated}.
* You can view a list of supported clusters on the *All Clusters* dropdown list. The supported clusters include {product-title}, {product-title} Service on AWS (ROSA), Azure Red Hat OpenShift (ARO), ROKS, and {product-dedicated}.
[id="ocp-4-12-multi-arch-console"]
===== Multi-architecture compute machines on the {product-title} web console
@@ -435,6 +435,15 @@ The OVN-Kubernetes network plugin includes a wider array of features than OpenSh
- Support for xref:../networking/ovn_kubernetes_network_provider/configuring-hybrid-networking.adoc#configuring-hybrid-networking[hybrid networks] for Windows containers
- Support for xref:../networking/hardware_networks/configuring-hardware-offloading.adoc#configuring-hardware-offloading[hardware offloading] to compatible NICs
There are also enormous scale, performance, and stability improvements in {product-title} {product-version} compared to prior versions.
If you are using the OpenShift SDN network plugin, note that:
* Existing and future deployments using OpenShift SDN continues to be supported.
* OpenShift SDN remains the default on {product-title} versions earlier than {product-version}.
* As of {product-title} {product-version}, OpenShift SDN is a supported installation-time option.
* OpenShift SDN remains feature frozen.
For more information about OVN-Kubernetes, including a feature comparison matrix with OpenShift SDN, see xref:../networking/ovn_kubernetes_network_provider/about-ovn-kubernetes.adoc#about-ovn-kubernetes[About the OVN-Kubernetes network plugin].
For information on migrating to OVN-Kubernetes from OpenShift SDN, see xref:../networking/ovn_kubernetes_network_provider/migrate-from-openshift-sdn.adoc#migrate-from-openshift-sdn[Migrating from the OpenShift SDN network plugin].
@@ -661,9 +670,9 @@ For more information, see xref:../networking/network_observability/network-obser
If you configured and deployed your hosting service cluster, you can now deploy the SR-IOV Operator for a hosted cluster. For more information, see xref:../networking/hardware_networks/configuring-sriov-operator.adoc#sriov-operator-hosted-control-planes_configuring-sriov-operator[Deploying the SR-IOV Operator for hosted control planes].
[id="ocp-4-12-nw-api-ingress-ipv6-support"]
==== Support for IPv6 virtual IP (VIP) addresses for the Ingress VIP and API VIP services
==== Support for IPv6 virtual IP (VIP) addresses for the Ingress VIP and API VIP services
With this update, in installer-provisioned infrastructure clusters, the `ingressVIP` and `apiVIP` configuration settings in the `install-config.yaml` file are deprecated. Instead, use the `ingressVIPs` and `apiVIPs` configuration settings. These settings support dual-stack networking for applications that require IPv4 and IPv6 access to the cluster by using the Ingress VIP and API VIP services. The `ingressVIPs` and `apiVIPs` configuration settings use a list format to specify an IPv4 address, an IPv6 address, or both IP address formats. The order of the list indicates the primary and secondary VIP address for each service. The primary IP address must be from the IPv4 network when using dual stack networking.
With this update, in installer-provisioned infrastructure clusters, the `ingressVIP` and `apiVIP` configuration settings in the `install-config.yaml` file are deprecated. Instead, use the `ingressVIPs` and `apiVIPs` configuration settings. These settings support dual-stack networking for applications that require IPv4 and IPv6 access to the cluster by using the Ingress VIP and API VIP services. The `ingressVIPs` and `apiVIPs` configuration settings use a list format to specify an IPv4 address, an IPv6 address, or both IP address formats. The order of the list indicates the primary and secondary VIP address for each service. The primary IP address must be from the IPv4 network when using dual stack networking.
[id="ocp-4-12-storage"]
=== Storage