4.6 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.6 of Red Hat OpenShift on IBM Cloud, released 09 Jun 2021. This version is based on Kubernetes version 1.19.

Looking for general information about updating clusters, or information on a different version? See Red Hat OpenShift on IBM Cloud version information.

Kubernetes version 1.19 certification badge

Red Hat OpenShift on IBM Cloud is a Certified Kubernetes product for version 1.20 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.6. 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.6.
Supported?	Red Hat OpenShift / Kubernetes version	Release date	Unsupported date
Supported	4.6 / 1.19	17 Feb 2021	Oct 27 2022 `†`

Preparing to update

Review changes that you might need to make when you update a cluster to version 4.6. 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.

Changes to make before you update the master to Red Hat OpenShift 4.6
Type	Description
Kubernetes snapshot CRDs	IBM Cloud Kubernetes Service installs Kubernetes snapshot custom resource definition (CRD) version `v1beta1`. If you use other Kubernetes snapshot CRD versions `v1` or `v1alpha1`, you must change the version to `v1beta1`. To check the currently installed version of your snapshot CRDs, run `grep snapshot.storage.k8s.io <<(kubectl get apiservices)`. Follow the Kubernetes documentation to Upgrade from v1alpha1 to v1beta1 to make sure that your snapshot CRDs are at the correct `v1beta1` version. The steps to downgrade from version `v1` to `v1beta1` are the same as those to upgrade from `v1alpha1`. Do not follow the instructions to upgrade from version `v1beta1` to version `v1`.
VPC clusters: App URL character length	DNS resolution is managed by the cluster's virtual private endpoint (VPE), which can resolve URLs up to 130 characters. If you expose apps in your cluster with URLs, such as the Ingress subdomain or Red Hat OpenShift routes, ensure that the URLs are 130 characters or fewer. For example, if you use an autogenerated route name in the format `<service_name>-<project>.<cluster_name>-<random_hash>-0000.<region>.containers.appdomain.cloud` that exceeds 130 characters, you might need to create a route that uses a shorter, custom subdomain instead.
Unsupported: Deprecated and removed Red Hat OpenShift features	For more information, review the Red Hat OpenShift version 4.6 deprecated and removed features.