OpenShift Dedicated Life Cycle

Overview

Red Hat provides a published product life cycle for Red Hat OpenShift Dedicated in order for customers and partners to effectively plan, deploy, and support their applications running on the platform. Red Hat publishes this life cycle in order to provide as much transparency as possible and may make exceptions from these policies as conflicts may arise.

The lifecycle of Red Hat OpenShift Dedicated follows a release-driven, phased approach where a single, minor version is available and will be supported at any one time.

Red Hat OpenShift Dedicated is a managed instance of Red Hat OpenShift and maintains an independent release schedule. More details about the managed offering can be found in the Service Definition. The availability of Security Advisories and Bug Fix Advisories for a specific version are dependent upon Red Hat OpenShift Container Platform’s lifecycle policy and subject to the Red Hat OpenShift Dedicated maintenance schedule.

Definitions

Version format Major Minor Patch major.minor.patch
  x y z x.y.z
Example 4 5 21 4.5.21

Minor Releases or Y Releases: They will be referred to only as Minor Releases or Y-Releases (x.Y.z).

Example Minor/Y Releases:

  • "Minor release 4" -> 4.4.x
  • "Minor release 5" -> 4.5.x
  • "Minor release 6" -> 4.6.x

Patch Releases or Z Releases: They will be referred to only as Patch Releases or Z-Releases (x.y.Z).

Example Minor/Z Releases:

  • "Patch release 14 of Minor release 5" -> 4.5.14
  • "Patch release 25 of Minor release 5" -> 4.5.25
  • "Patch release 26 of Minor release 6" -> 4.6.26

Major Versions (X.y.z)

Major (e.g. version 4) versions of Red Hat OpenShift Dedicated are supported for one year following the release of a subsequent major version or the retirement of the product. Existing customers are allowed to create new clusters with a major version for 6 months following the release of a subsequent major version.

For example, if a version 5 were made available on Red Hat OpenShift Dedicated on 1st of January, version 4 would be allowed to continue running on managed clusters for 12 months, until the 31st of December. After this time clusters would need to be upgraded or migrated to version 5. Additionally, version 4 would continue to be installable by existing customers for 6 months after a version 5 was made available, until the 30th of June.

Minor versions (x.Y.z)

Red Hat supports two minor versions of the major release.

  • Y: The latest available minor release. For example 4.8
  • Y - 1: The previous minor version. For example 4.7

Once a new minor version is released, clusters running Y-2 must upgrade their cluster within 30 days. Any cluster remaining on Y-2 thirty days after notification of release will be automatically updated to the latest Y-1 release during the customer’s defined upgrade window.

Example: Customer’s cluster currently running on 4.5.18.
Latest version for 4.6 is 4.6.27.
On February 25th, 4.7.0 is released and customer is notified.

The cluster must be upgraded to at least 4.6.27 by March 25th.
If the upgrade has not been performed then the cluster will be automatically updated to 4.6.27.

Patch versions (x.y.Z)

During the period in which a minor release is supported all OpenShift Container Platform patch releases will be supported unless otherwise specified.

For reasons of platform security and stability a patch release may be deprecated, which would prevent installations on or upgrades to that version.

Example:
4.7.6 is found to contain a critical CVE. This release will be removed from the supported patch release list.

Install Policy

While Red Hat recommends installation of the latest support release, Red Hat OpenShift Dedicated will support installation of any supported release as covered by the above policy.

Mandatory Upgrades

In the exceptional case that a critical CVE or other bug that significantly impacts the stability and operation of the cluster is identified by Red Hat, the customer will be required to upgrade to the next supported patch release within 7 days. If the upgrade to the next supported patch release has not been performed within seven days of notification, the cluster will be automatically updated to the latest patch release during the customer’s defined upgrade window.

Life Cycle Dates (v4)

Version General Availability End of Life
4.6 Oct 27, 2020 Release of 4.8 + 30 days
4.5 Sep 23, 2020 Release of 4.7 + 30 days
4.4 Sep 15, 2020 Nov 26, 2020
4.3 Feb 19, 2020 Oct 23, 2020
4.2 Nov 12, 2019 Oct 15, 2020
4.1 June 11, 2019 Mar 20, 2020