Overview

Red Hat provides a published product life cycle for Red Hat OpenShift Service on AWS 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 might make exceptions from these policies as conflicts arise.

Red Hat OpenShift Service on AWS 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 Red Hat OpenShift Service on AWS 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 Red Hat OpenShift Service on AWS maintenance schedule.

Definitions

Table 1. Version reference
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).

Examples
  • "Major release 5" → 5.y.z

  • "Major release 4" → 4.y.z

  • "Major release 3" → 3.y.z

Minor releases or Y-releases

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

Examples
  • "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).

Examples
  • "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 Service on AWS, 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 Service on AWS on January 1, version 4 would be allowed to continue running on managed clusters for 12 months, until December 31. After this time, clusters would need to be upgraded or migrated to version 5.

Minor versions (x.Y.z)

Starting with the 4.8 OpenShift Container Platform minor version, Red Hat supports all minor versions within a 9 month period following general availability of the given minor version. Patch versions do not affect the 9 month supportability period.

Customers are notified 60, 30, and 15 days prior to the end of the 9 month period. Clusters must be upgraded to a supported minor version prior to the end of the 9 month period, or the cluster will enter a "Limited Support" status.

Example
  1. A customer’s cluster is currently running on 4.8.14. The 4.8 minor version became generally available on July 27, 2021.

  2. On Feb 26, March 28, and April 12, 2022, the customer is notified that their cluster will enter "Limited Support" status on April 27, 2022 if the cluster has not already been upgraded to a supported minor version.

  3. The cluster must be upgraded to 4.9 or later by April 27, 2022.

  4. If the upgrade has not been performed, the cluster will be flagged as being in a "Limited Support" status.

Patch versions (x.y.Z)

During the period in which a minor version is supported, Red Hat supports all OpenShift Container Platform patch versions 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 may be asked to upgrade the cluster to a supported version when requesting support. Additionally, Red Hat does not make any runtime or SLA guarantees for clusters outside of the supported versions list at the end of their 9 month end of life cycle date.

Red Hat provides commercially reasonable support 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 may 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.

Installation policy

While Red Hat recommends installation of the latest support release, Red Hat OpenShift Service on AWS supports 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

Version General availability End of life

4.9

Oct 18, 2021

Jul 18, 2022

4.8

Jul 27, 2021

Apr 27, 2022

4.7

Mar 24, 2021

Dec 17, 2021 [1]


1. 4.7 minor version follows previous Y-1 life cycle