4.13 version information and update actions

This version is deprecated. Update your cluster to a supported version as soon as possible.

Review information about version 4.13 of Red Hat OpenShift on IBM Cloud. This version is based on Kubernetes version 1.26.

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.13 blog.

Kubernetes version 1.26 certification badge

Red Hat OpenShift on IBM Cloud is a Certified Kubernetes product for version 1.26 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.13. 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.

Release history for Red Hat OpenShift on IBM Cloud version 4.13.
Supported?	Red Hat OpenShift / Kubernetes version	Release date	Unsupported date
Supported	4.13 / 1.26	14 June 2023	26 February 2025`†`

Preparing to update

Review changes that you might need to make when you update a cluster to version 4.13. This information summarizes updates that are likely to have an 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.

Cluster master access for VPC clusters with a private service endpoint changed significantly from version 4.12. Before updating a cluster of this type, review the following information and consider what changes you must make before upgrading your cluster. Also, consider this before creating a new 4.13 cluster with only a private service endpoint.

Changes to make before you update the master to Red Hat OpenShift 4.13
Type	Description
Unsupported: Deprecated and removed OpenShift features	For more information, review the OpenShift version 4.13 deprecated and removed features and Preparing to update to OpenShift Container Platform 4.13 for possible actions required.
Known OpenShift issues	For more information, review the OpenShift version 4.13 known issues for possible actions required.
Updated worker node metrics configuration	In order for your cluster to maintain pod and node metrics during the update, your cluster master must be at fix pack version 4.12.16_1545_openshift or later and your cluster worker nodes must be at fix pack version 4.12.19_1546_openshift or later.
Access changes for VPC clusters with a private service endpoint only	Previously In VPC clusters with a private service endpoint only, if you wanted to access the cluster through the Openshift Console, run terraform scripts, create a `kubeconfig` file via `oc login`, or make similar API calls that required oauth to get a token, then you needed to access the private service endpoint, which was in the format `https://cX00.private.us-south.containers.cloud.ibm.com:port`. This setup only required access to the IBM Cloud private network `166.8.0.0/14`. Now In Openshift 4.13 this behavior has changed. In addition to accessing the IBM Cloud private network, the client system also needs access to the VPC's private DNS resolution to be able to connect to IP addresses in the VPC that the cluster is in. This is due to a change to use the VPE gateway DNS name of the form `clusterID.vpe.private.us-south.containers.cloud.ibm.com:port` for access to the apiserver and the oauth server. Now, to access the Red Hat OpenShift console, run `oc login`, or make similar API calls, the client system must be able to resolve the VPE gateway DNS name and reach the VPE gateway in the VPC. You must setup your VPC VPN or other networking solution to be able to access the VPE gateway. For more information, see Accessing VPC clusters through the VPE gateway. It is important to set the IBM Cloud VPC Private DNS server addresses (`161.26.0.7` and `161.26.0.8`) as DNS resolvers and set routing towards IaaS services (`161.26.0.0/16`). However, if you don't want to use the new behavior, you can update your cluster, then set the Oauth access type for your cluster back to the `legacy` behavior to use the Private service endpoint. For more information, see Setting the OAuth access type for VPC clusters.