4.18 version information and update actions
Review information about version 4.18 of Red Hat OpenShift on IBM Cloud. This version is based on Kubernetes version 1.31.
Looking for general information about updating clusters, or information on a different version? See Red Hat Red Hat OpenShift on IBM Cloud version information and the version 4.18 release notes.
Red Hat OpenShift on IBM Cloud is a Certified Kubernetes product for version 1.31 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.18. 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 |
|---|---|---|---|
| Supported | 4.18 / 1.31 | 23 May 2025 | 26 May 2027† |
Preparing to update
Review changes that you might need to make when you update a cluster to version 4.18. This information summarizes updates that are likely to have an impact on deployed apps when you update.
Portworx does not yet support version 4.18. Do not upgrade your cluster to version 4.18 if your apps use Portworx. For more information, see Supported OpenShift versions
The Satellite Location Sizing Requirements for hosting Red Hat OpenShift on IBM Cloud version 4.18 clusters are now the same regardless of the Location being RHEL (non-CoreOS) or CoreOS-enabled. The requirements for the Location nodes should now follow those for CoreOS-enabled locations.
Update before master
The following table shows the actions that you must take before you update the cluster master.
For clusters that run version 4.18 or later, you can use the oc adm upgrade status command to check the update status of your cluster master during a master version update. For more information, see Viewing cluster upgrade status with the oc adm upgrade status command.
| Type | Description |
|---|---|
| Preparing to update OpenShift | For more information, review the Preparing to update to OpenShift Container Platform 4.18 for possible actions required. The etcd backup, version selection, and SDN removal upgrade preparation actions do not apply to Red Hat OpenShift on IBM Cloud clusters since etcd backups and version selection actions are handled for you, and Calico is used instead of SDN. |
| Deprecated and removed OpenShift features | For more information, review the OpenShift Container Platform version 4.18 deprecated and removed features for possible actions required. |
| Known OpenShift issues | For more information, review the OpenShift Container Platform version 4.18 known issues for possible actions required. |
| Upgrade requires OpenShift cluster version currency | A cluster master upgrade will be canceled if the OpenShift cluster version status indicates that an update is already in progress. See Why does OpenShift show the cluster version is not up to date? for details. |
| Upgrade requires resolution to OpenShift cluster version upgradeable conditions | A cluster master upgrade will be canceled if the OpenShift cluster version Upgradeable status condition indicates that the cluster is not upgradeable. To determine if the cluster is upgradeable, see Checking the Upgradeable status of your cluster. |
| RHEL 9 is the default operating system | RHEL 9 is the default operating system for Red Hat OpenShift on IBM Cloud version 4.18 Classic or VPC clusters. Upgrading a cluster to version 4.18 does not change the operating system for an existing worker pool. For more information and possible migration actions related to RHEL 9, see Migrating to a new Red Hat Enterprise Linux version. |
Checking the Upgradeable status of your cluster
Run the following command to check the Upgradeable status of your cluster.
oc get clusterversion version -o json | jq '.status.conditions[] | select(.type == "Upgradeable")'
Example output where the Upgradeable status is False.
{
"lastTransitionTime": "2024-11-17T19:29:34Z",
"message": "Cluster operator operator-lifecycle-manager should not be upgraded between minor versions: ClusterServiceVersions blocking cluster upgrade: default/test is incompatible with OpenShift minor versions greater than 4.16",
"reason": "IncompatibleOperatorsInstalled",
"status": "False",
"type": "Upgradeable"
}
If the Upgradeable status is False, the condition information provides instructions that must be followed before upgrading.