This life cycle page refers only to the latest major version of Red Hat OpenShift. Information regarding OpenShift 3 and other, older versions of OpenShift can be found on the Life Cycle page for non-current OpenShift versions.


Red Hat OpenShift Container Platform Life Cycle Policy

Overview

Red Hat provides a published product life cycle for Red Hat OpenShift Container Platform (“OpenShift” or “OCP”), in order for customers and partners to effectively plan, deploy, and support their infrastructure. Red Hat publishes this life cycle in an effort to provide as much transparency as possible and may make exceptions from these policies as conflicts may arise.

All released errata will remain accessible to active subscribers across the entire life cycle.

With the introduction of OpenShift 4, Red Hat transitioned the product lifecycle from a traditional, time delineated life cycle in favor of a release driven, phased life cycle. Life Cycles are distinct by OpenShift major version:

  • Red Hat OpenShift Container platform v3, providing three support phases for the major version; Full Support, Maintenance Support, and an Extended Life Phase, each spanning a fixed calendar term. Detailed life cycle information can be found on the Life Cycle page for non-current OpenShift versions.
  • Red Hat OpenShift Container platform v4, providing a modern release driven, phased life cycle, where in at least 3 minor versions could be supported at any point in time. The time period of support is determined by the future release schedule. Red Hat aims to forecast these at a 3 month cadence, providing customers ample opportunity to plan.

OpenShift Container Platform v4

This life cycle encompasses stated support phases, delimited by the minor releases of Red Hat OpenShift Container Platform. The life cycle for each minor version (e.g. 4.1) of OpenShift is split into production phases, each identifying the various levels of maintenance over a period of time from the initial release date.

With the introduction of Red Hat OpenShift Container Platform v4, the major version of a release (e.g. 4.x) will continue to be available for a minimum of three years from initial General Availability (GA), this 3 year period is split into two phases; GA phase 1 and GA phase 2:

  • GA Phase 1 - Available for a minimum of 2 years from the first major version of the release. This phase ends when a newer major version becomes available. During GA phase 1, minor releases will be available and supported as with Full or Maintenance terms
  • GA Phase 2 - Available for a fixed, 1 year time period. This phase commences at the end of GA Phase 1, throughout this phase only the last minor and relevant EUS release will be supported per the Maintenance Support terms
OCP v4 Life Cycle

Life Cycle Phases

Full Support

This Phase begins at the GA/release of the minor version and ends 1 calendar month after the GA of the superseding minor release (roughly a four month period). The one month overlapping period permits a customer to remain in the full support phase across two minor releases.

Full support is provided according to the published Scope of Coverage and Service Level Agreement. Likewise, Development Support is provided according to the published Scope of Coverage and Service Level Agreement.

During the Full Support Phase, qualified Critical and Important Security Advisories (RHSAs) and Urgent and Selected High Priority Bug Fix Advisories (RHBAs) will be released as they become available; all other available fix and qualified patches may be released via periodic updates. In order to receive security and bug fixes, customers are expected to upgrade their OpenShift environment to the most current supported micro (4.x.z) version.

Maintenance Support

This Phase begins a month after the GA/release of the superseding minor version and ends when the 3rd superseding minor version is released.

During the Maintenance Support phase, qualified Critical and Important Security Advisories (RHSAs) and Urgent and Selected High Priority Bug Fix Advisories (RHBAs) may be released as they become available. Other Bug Fix (and Enhancement (RHEA) Advisories may be released at Red Hat’s discretion, but should not be expected.

At the end of the maintenance support phase, software and documentation will continue to be available to customers however no technical support will be provided except assistance to upgrade to a supported version. Full functionality of an OpenShift cluster(s) may require access to hosted services provided by Red Hat, the availability of these services cannot be guaranteed for unmaintained and unsupported versions of OpenShift.

Extended Update Support

Red Hat will denote specific minor releases as Extended Update Support (EUS) releases. These will be outlined on this page, and as part of product release notes. Extended update support will provide maintenance support coverage for a release, replacing the release delimited maintenance support phase with a fixed 14 months maintenance support phase. Inclusive of the full support phase, this provides customers with an approximate 18 months total support coverage for a minor version.

For an EUS release, qualified Critical and Important Security Advisories (RHSAs) and Urgent and Selected High Priority Bug Fix advisories (RHBAs) will be released as they become available as part of the Full Support phase. Following this is the Maintenance support phase for a fixed time period of 15 months, throughout this phase qualified Critical and Important Security Advisories (RHSAs) and Urgent and Selected High Priority Bug Fix errata Advisories (RHBAs) may be released as they become available. Other Bug fix and Enhancement (RHEA) Advisories may be released at Red Hat’s discretion, but should not be expected.

At the end of the Extended Updated Support phase, software and documentation will continue to be available to customers. Full functionality of an OpenShift cluster may require access to hosted services provided by Red Hat, the availability of these services cannot be guaranteed for unmaintained and unsupported versions of OpenShift.

Life Cycle Dates

Layered and Dependant Components

RHEL CoreOS

RHEL CoreOS is a component of OpenShift 4 and is maintained per the OpenShift life cycle. Each release of OpenShift includes a corresponding stream of RHEL CoreOS.[8]

Layered Offering On OpenShift

OpenShift Container Platform provides a variety of runtimes and application frameworks (provided directly from Red Hat) or our partners. All of the layered content or container offerings provided by Red Hat, our partners and/or third party providers maintain an independent lifecycle from OpenShift. As a result, it is important that you check with the content providers to see how that content is tested, certified and supported on the particular version of OpenShift you are running.

For Red Hat provided products or offerings we maintain this lifecycle and testing information in the following locations:

Software Classification Provided Tools/Functionality Life Cycle / Tested Configuration Links
Red Hat Software Collections PHP, Perl, Python, Ruby, node.JS, Postgres, MySQL, MongoDB https://access.redhat.com/support/policy/updates/rhscl
JBoss Products Add-ons EAP, EWS/JWS, Fuse, AMQ, BRMS, Data Grid https://access.redhat.com/support/policy/updates/jboss_notes

OpenShift Container Storage

Commencing with OpenShift v4.2, OpenShift Container Storage (OCS) v4 is provided and available as an optional, installable component. Comprising of the upstream projects Rook-Ceph and NooBaa, OpenShift Container Storage is not shipped inclusive as part of the OpenShift Container Platform subscription and it needs its own subscription and supported per the Red Hat production terms of support[5&6].

To allow for an increased frequency in features and fixes, OpenShift Container Storage maintains a release cadence independent of the OpenShift minor version release stream. Red Hat aims to forecast OpenShift Container Storage releases at a 3-month cadence, providing customers ample opportunity to plan for upgrades.

OpenShift Container Storage provides two support phases throughout the availability of a minor release; Full Support and Maintenance Support. The support level throughout each of the life cycle phases is denoted as part of the OpenShift v4 life cycle.

Support for OpenShift Container Storage is only available for a corresponding minor version of OpenShift in its Full Support phase, as well as the superseding minor version of OpenShift, whilst OCS is in Full Support phase. The availability of support on any level for OCS is subject to the overarching version of OpenShift for which it is released, no support is offered for OCS or OpenShift beyond the maintenance or EUS phase boundary for OpenShift.

Support Phase Boundaries

The OCS Full Support Phase commences at the GA release date of the minor version and ends one calendar month after the GA of the superseding minor OCS release (roughly a four-month period). The one-month overlapping period permits a customer to remain in the full support phase across two minor releases.

Maintenance Support Phase begins a month after the GA/release of the superseding minor version and ends when the 3rd superseding minor version is released.

Extended Update Support will be available for select OpenShift Container Storage releases. These releases will be outlined on this page and as part of release notes. Extended update support will provide maintenance support coverage for a release of OCS for the period in which EUS is available for an OpenShift release.

OpenShift Container Storage - Support Phase Dates and OpenShift Support Matrix
OCS Version OCP Version(s) General Availability (Full Support) Beginning of OCS Maintenance Support End of OCS Maintenance Support
4.2 4.2 Jan 14, 2020 May 14, 2020 Release of OCS 4.5
4.3 4.3 Apr 14, 2020 Jul 4, 2020 Release of OCS 4.6
4.4 4.4 Jun 4, 2020 Release of OCS 4.5+1 month Release of OCS 4.7

More information on the support for versions of OCS can be found in the OCS Interoperability Matrix.

OpenShift Service Mesh

Commencing with OpenShift 4.1, OpenShift Service Mesh (OSSM) is provided and available as an optional, installable component. Comprising of the upstream projects; Istio, Jaeger and Kiali, OpenShift Service Mesh is shipped inclusive as part of the OpenShift Container Platform subscription[7] and supported per the Red Hat production terms of support[5&6].

To allow for an increased frequency in features and fixes, OpenShift Service Mesh maintains a release cadence independent to the OpenShift minor version release stream. Red Hat aims to forecast OpenShift Service Mesh releases at a 3 month cadence, providing customers ample opportunity to plan for upgrades.

OpenShift Service Mesh provides two support phases throughout the availability of a minor release; Full Support and Maintenance Support. The support level throughout each of the life cycle phases is denoted as part of the OpenShift v4 life cycle.

Support for OpenShift Service Mesh is only available for a corresponding minor version of OpenShift in its Full Support phase, as well as the superseding minor version of OpenShift, whilst OSSM is in Full Support phase. The availability of support on any level for OSSM is subject to the overarching version of OpenShift for which it is released, no support is offered for OSSM or OpenShift beyond the maintenance or EUS phase boundary for OpenShift.

Support Phase Boundaries

The OSSM Full Support Phase commences at the GA release date of the minor version and ends one calendar month after the GA of the superseding minor OSSM release (roughly a four month period). The one month overlapping period permits a customer to remain in the full support phase across two minor releases.

Maintenance Support Phase begins a month after the GA/release of the superseding minor version and ends when the 3rd superseding minor version is released.

Extended Update Support will be available for select Service Mesh releases. These releases will be outlined on this page, and as part of release notes. Extended update support will provide maintenance support coverage for a release of OSSM for the period in which EUS is available for an OpenShift release.

OpenShift Service Mesh - Support Phase Dates and OpenShift Support Matrix
Version OCP Version(s) General Availability (Full Support) Beginning of Maintenance Support End of Maintenance Support
1.1 4.3, 4.4 Apr 9th, 2020 Release of 1.2 + 1 month Release of 1.4
1.0 4.1, 4.2, 4.3 Sept 4th, 2019 May 9th, 2020 Release of 1.3

OpenShift Serverless

To allow for an increased frequency in features and fixes, OpenShift Serverless maintains a release cadence independent of the OpenShift minor version release stream. Red Hat aims to forecast OpenShift Serverless releases at a 3 month cadence, providing customers ample opportunity to plan for upgrades.

OpenShift Serverless provides two support phases throughout the availability of a minor release; Full Support and Maintenance Support. The support level throughout each of the life cycle phases is denoted as part of the OpenShift v4 life cycle.

Support for OpenShift Serverless is only available for a corresponding minor version of OpenShift in its Full and Maintenance Support phase. The availability of support on any level for OpenShift Serverless is subject to the overarching version of OpenShift for which it is released; no support is offered for OpenShift Serverless or OpenShift beyond the maintenance or EUS phase boundary for OpenShift.

Support Phase Boundaries

The OpenShift Serverless Full Support Phase commences at the GA release date of the minor version and ends one calendar month after the GA of the superseding minor Serverless release (roughly a four month period). The one month overlapping period permits a customer to remain in the full support phase across two minor releases.

Maintenance Support Phase begins a month after the GA/release of the superseding minor version and ends when the 3rd superseding minor version is released.

Extended Update Support will be available for select Serverless releases. These releases will be outlined on this page, and as part of release notes. Extended update support will provide maintenance support coverage for a release of Serverless for the period in which EUS is available for an OpenShift release.

OpenShift Serverless - Support Phase Dates and OpenShift Support Matrix
Serverless Version OCP Version(s) General Availability (Full Support) Beginning of Maintenance Support End of Maintenance Support
1.7.0 4.3, 4.4 Apr 29th, 2020 Release of Serverless 1.8.0 + 1 month Release of Serverless 1.10.0

OpenShift Jaeger

Commencing with OpenShift 4.3, OpenShift Jaeger is provided and available as an optional, installable component. OpenShift Jaeger is shipped inclusive as part of the OpenShift Container Platform subscription[7] and supported per the Red Hat production terms of support[5&6].

To allow for an increased frequency in features and fixes, OpenShift Jaeger maintains a release cadence independent of the OpenShift minor version release stream.

OpenShift Jaeger is available through a single, rolling stream which is supported throughout the entire life cycle of OpenShift 4. For the duration of Openshift 4 GA Phase 1, the Jaeger release stream will continually rebase on stable upstream versions of Jaeger. Throughout this rolling stream, qualified Critical and Important Security errata advisories (RHSAs) and Urgent and Selected High Priority Bug Fix errata advisories (RHBAs) may be released as they become available, all other available fix and qualified patches may be released via periodic updates.

Support for OpenShift Jaeger commences with its initial release, the rolling stream is maintained with ‘Full Support’ coverage throughout OpenShift 4 GA Phase 1. During OpenShift 4 GA Phase 2, support coverage is only provided per OpenShift 4 ‘Maintenance Support’.

OpenShift Application and Cluster Migration Solutions

Commencing with OpenShift 4.2, Cluster Application Migration Tool (CAM) and Control Plane Migration Assistant (CPMA) are provided and available as an optional, installable component or set of tools that customers can use to assist in the migration of application workloads or cluster configuration from one version (source) of OpenShift to another (destination).

Comprising of the upstream projects; Velero and restic, the OpenShift Migration tools (CAM and CPMA) are shipped inclusive as part of the OpenShift Container Platform subscription[7] and supported per the Red Hat production terms of support[5&6]. Each tool defines a unique support matrix and set of boundaries for each version that is released.

Cluster Application Migration Tool (CAM)

The CAM Full Support Phase commences at the GA release date of the minor version and ends one calendar month after the GA of the superseding minor release (approximately a four month period). The overlapping one month period is to allow customers to remain in full support whilst they complete their upgrades on their existing release, rather than opt to use the newly released version.

During the Full Support Phase, qualified Critical and Important Security errata advisories (RHSAs) and Urgent and Selected High Priority Bug Fix errata advisories (RHBAs) may be released as they become available, all other available fix and qualified patches may be released via periodic updates.

Support Phase Boundaries

To provide constancy the CAM tools aim to support migration capabilities spanning back 6 minor versions of OpenShift. This allows for customers and partners to effectively plan efforts for the use of these tools in their environments. The availability of support on any level for CAM is subject to the overarching version of OpenShift for which CAM is supported, no support is offered for CAM or OpenShift beyond the supported phase boundary for OpenShift.

The CAM tools have its components broken up in a way so that each component can be supported in different OpenShift environments (source and target clusters) and across different OpenShift version, providing customers a wide range of migration options.

CAM components are broken down into 2 classifications (of components) based on where they can be installed, and where Red Hat will support these components running. The Migration-UI and Migration-Controller components are only supported on ‘destination’ cluster[s], while the Migration-Operator (Velero) is supported on both the ‘source’ and ‘destination’ cluster[s].

OpenShift Cluster Application Migration Tool (CAM) - Support Phase Dates
Version General Availability (Full Support) End of Maintenance Support
1.0 Supported OCP Source Cluster Versions Oct 16th, 2019 1 month after the release of 1.1
3.7, 3.9, 3.10, 3.11, 4.1, 4.2
Supported OCP Target Cluster Versions
4.2

Control Plane Migration Assistant (CPMA)

The CPMA Full Support Phase commences at the GA release date of the minor version, and ends one calendar month after the GA of the superseding minor release (approximately a four month period). The overlapping one month period is to allow customers to remain in full support whilst they complete their upgrades on their existing release, rather than opt to use the newly released version.

During the Full Support Phase, qualified Critical and Important Security errata advisories (RHSAs) and Urgent and Selected High Priority Bug Fix errata advisories (RHBAs) may be released as they become available, all other available fix and qualified patches may be released via periodic updates.

Support Phase Boundaries

The CPMA tool is reliant on the OpenShift support life cycle and is not supported beyond the denoted OpenShift 3.x life cycle. The CPMA tool will continue to get minor version updates, and with each release denote a minimum OCP version it is compatible with until OpenShift 3.x is no longer supported (enters End of Life Phase).

The CPMA tool is supported across differing OpenShift environments (source and target clusters) and across various OpenShift versions, providing a wide range of migration options. The supported source and target migration paths are denoted below.

OpenShift Control Plane Migration Assistant (CPMA) - Support Phase Dates
Version General Availability (Full Support) End of Maintenance Support
1.0 Supported OCP Source Cluster Versions Oct 16th, 2019 1 month after the release of 1.1
3.7, 3.9, 3.10, 3.11
Supported OCP Target Cluster Versions
4.1, 4.2

Footnotes

  1. Red Hat can choose to address critical or important bug fixes upon request, with significant business impact for the customer through a hot fix, as a temporary measure while the bug fix patch is being created.
  2. The latest Major and Minor releases are the primary source for software enhancements. Roll-ups, updates, and patches are specifically reserved for bug fixes.
  3. Latest security update information available at: https://access.redhat.com/site/security/updates/
  4. Red Hat provides Critical impact security fixes and selected urgent-priority bug fixes, if and when available.
  5. Scope of coverage available at: https://access.redhat.com/support/offerings/production/soc/
  6. Service level agreements available at: https://access.redhat.com/support/offerings/production/sla
  7. Availability limited to specific architectures.
  8. RHEL CoreOS version information available on the Tested Configurations Matrix: https://access.redhat.com/articles/4128421