4.10 version information and update actions
Review information about version 4.10 of Red Hat OpenShift on IBM Cloud. This version is based on Kubernetes version 1.23.
Version 4.10 is no longer supported. Update your cluster to at least version 4.11 as soon as possible.
If you have Portworx installed, follow the steps to upgrade your installation to use at least image version 2.11.4. For more information, see Upgrading Portworx to a specific version.
Gateway-enabled clusters on Classic infrastructure are deprecated and will be unsupported soon. The end of support dates are linked directly to the end of support of Red Hat OpenShift on IBM Cloud version 4.9. Gateway-enabled clusters are not supported on version 4.10 and later. If your cluster is gateway-enabled cluster, plan to create a new cluster before support ends. If you need similar functionality, consider creating a cluster on VPC infrastructure.
Extended update support (EUS) updates are not available at this time for Red Hat OpenShift on IBM Cloud version 4.10 clusters.
Red Hat OpenShift on IBM Cloud is a Certified Kubernetes product for version 1.23 under the CNCF Kubernetes Software Conformance Certification program. Kubernetes® is a registered trademark of The Linux Foundation in the United States and other countries, and is used pursuant to a license from The Linux Foundation.
Release timeline
The following table includes the expected release timeline for version 4.10. You can use this information for planning purposes, such as to estimate the general time that the version might become unsupported.
Dates that are marked with a dagger (†) are tentative and subject to change.
| Supported? | Red Hat OpenShift / Kubernetes version | Release date | Unsupported date |
|---|---|---|---|
| Unsupported | 27 April 2022 | 4.10 / 1.23 | 27 April 2022 |
Preparing to update
If you want to upgrade a 4.9 cluster with RHEL 7 worker nodes to 4.10, replace your RHEL 7 worker nodes with RHEL 8 worker nodes before you follow the steps to upgrade to version 4.10.
- Gateway-enabled clusters
- Classic clusters created with the
--gateway-enabledoption do not support RHEL 8 worker nodes, and therefore are not supported for version 4.10. You cannot update your cluster to version 4.10 if it has the gateway-enabled cluster controller installed.
Update before master
The following table shows the actions that you must take before you update the cluster master.
| Type | Description |
|---|---|
| Unsupported: Deprecated and removed Red Hat OpenShift features | For more information, review the Red Hat OpenShift version 4.10 deprecated and removed features. |
| Kubernetes API server metrics job name changed | Kubernetes API server metrics now use job kube-apiserver rather than cluster-version-operator. Update any custom metrics and alerts to use the new job name. |
| Deprecated: RHEL 7 | RHEL 7 is deprecated in version 4.10. Migrate your worker nodes to RHEL 8. |
Updated default container network sysctls |
New containers running on the pod network have the following sysctl tuning applied by default: net.ipv4.tcp_keepalive_intvl=15, net.ipv4.tcp_keepalive_probes=6 and net.ipv4.tcp_keepalive_time=40.
If your apps rely on the previous defaults, you must update your app deployment to customize the sysctl settings. For more information, see Optimizing network keepalive sysctl settings. |
Migrating your worker nodes to RHEL 8
With the release of RHEL 8, the use of RHEL 7 worker nodes is deprecated in clusters that run version 4.10. You cannot upgrade RHEL 7 worker nodes to RHEL 8.
Instead, you must provision a new worker pool and then delete the previous worker pool. In versions 4.10 and later, worker nodes in the new worker pool run RHEL 8 by default. See Migrating to a new Red Hat Enterprise Linux version.