OpenShift Dedicated Life Cycle

Overview

Red Hat provides a published product life cycle for 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 arise.

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 OpenShift Dedicated service definition. The availability of Security Advisories and Bug Fix Advisories for a specific version are dependent upon the Red Hat OpenShift Container Platform life cycle policy and subject to the 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

Major releases or X-releases:

Referred to only as major releases or X-releases (X.y.z).

Example:

  • "Major release 5" -> 5.y.z
  • "Minor release 4" -> 4.y.z
  • "Minor release 3" -> 3.y.z

Minor releases or Y-releases:

Referred to only as minor releases or Y-releases (x.Y.z).

Example:

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

Patch Releases or Z-Releases:

Referred to only as Patch Releases or Z-Releases (x.y.Z).

Example:

  • "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 versions of Red Hat OpenShift Dedicated, for example version 4, are supported for one year following the release of a subsequent major version or the retirement of the product.

Example

If 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.

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

After an upgrade path from the previous minor version (Y-1) to the latest minor version (Y) is available, clusters running Y-2 must upgrade their cluster within a 30 day grace period. Any cluster remaining on Y-2 30 days after notification of upgrade availability will be classified as being in limited support status until the cluster is upgraded to a supported release.

Example

  1. A customer’s cluster is currently running on 4.5.18. The latest version for 4.6 is 4.6.27.
  2. On February 25, 4.7.2 is released as an available upgrade path from 4.6.27 and the customer is notified.
  3. The cluster must be upgraded to 4.6.27 or later by March 25.
  4. If the upgrade has not been performed, then the cluster will have SRE alerting disabled and will be unsupported until it is upgraded to 4.6.27 or later.

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 of that release and trigger mandatory upgrades off that release.

Example

  1. 4.7.6 is found to contain a critical CVE.
  2. Any releases impacted by the CVE will be removed from the supported patch release list. In addition, any clusters running 4.7.6 will be scheduled for automatic upgrades within 48 hours.

Limited support status

While operating outside of the supported versions list, you might be asked to upgrade the cluster to a supported version when requesting support, unless you are within the 30-day grace period after version deprecation. Additionally, Red Hat does not make any runtime or SLA guarantees for clusters outside of the supported versions list at the end of the 30-day grace period.

Red Hat will provide best effort to ensure an upgrade path from an unsupported release to a supported release is available. However, if a supported upgrade path is no longer available, you might be required to create a new cluster and migrate your workloads.

Supported versions exception policy

Red Hat reserves the right to add or remove new or existing versions, or delay upcoming minor release versions, that have been identified to have one or more critical production impacting bugs or security issues without advance notice.

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 preceding policy.

Mandatory Upgrades

In the event that a Critical or Important CVE, or other bug identified by Red Hat, significantly impacts the security or stability of the cluster, the customer must upgrade to the next supported patch release within 48 hours.

In extreme circumstances and based on Red Hat’s assessment of the CVE criticality to the environment, if the upgrade to the next supported patch release has not been performed within 48 hours of notification, the cluster will be automatically updated to the latest patch release to mitigate potential security breach or instability.

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