4.8 version information and update actions
This version is no longer supported. Update your cluster to a supported version as soon as possible.
Review information about version 4.8 of Red Hat OpenShift on IBM Cloud, released 29 Sept 2021. This version is based on Kubernetes version 1.21.
Looking for general information about updating clusters, or information on a different version? See Red Hat OpenShift on IBM Cloud version information.
Red Hat OpenShift on IBM Cloud is a Certified Kubernetes product for version 1.21 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.8. 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 |
|---|---|---|---|
| Deprecated | 4.8 / 1.21 | 29 September 2021 | 27 April 2023† |
Preparing to update
Review changes that you might need to make when you update a cluster to version 4.8. This information summarizes updates that are likely to have and impact on deployed apps when you update.
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 Red Hat OpenShift version 4.8 deprecated and removed features. |
| Container runtime default security context capabilities | The container runtime (for example, CRI-O) default security context capabilities have been changed to match Red Hat OpenShift Container Platform (OCP). NET_RAW and SYS_CHROOT have been removed. This brings the
security behavior of containers in line with OCP. If your app requires either of these capabilities and does not list them in the container or pod securityContext, then the app must be changed to include these capabilities.
If these changes are not made, your microservices might fail to start and you might see a permission denied error. Applications developed for OCP already have the necessary changes. |
| Strongswan users | If you are using Strongswan in your cluster, then update at least version 2.7.11 of Strongswan before you update your cluster master to Red Hat OpenShift 4.8. In versions of Strongswan earlier than 2.7.11, certain Strongswan configuration options do not work with the Red Hat OpenShift 4.8 master. |