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.

Red Hat OpenShift container platform v4 provides a time-delineated, phased life cycle, where in at least 4 minor versions can be supported at any time. The time period of support is fixed from the point of minor version release and offers varying levels of support and maintenance. Red Hat aims to forecast releases at a 4 month cadence, providing customers ample opportunity to plan.

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

Life Cycle Phases

Full Support

This phase begins at the GA/release of the minor version and ends after a 6 month period OR 90 days after the GA of the superseding minor release, whichever is later.

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) will be released as they become available. 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

For OpenShift 4.12 releases and newer
This phase commences after the Full Support phase for the respective minor version and ends at 18 months after GA.

During the Maintenance Support phase, qualified Critical and Important Security Advisories (RHSAs) will be released as they become available. 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.

For OpenShift releases 4.7 to 4.11, inclusive
This phase commences after the Full Support phase for the respective GA and has a duration of 12 months. For instances where the full support phase for the version is beyond 6 months, the duration of the maintenance phase is reduced so the accumulated Full and Maintenance support phases for a release are 18 months.

During the Maintenance Support phase, qualified Critical and Important Security Advisories (RHSAs) will be released as they become available. 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

Commencing with OpenShift Container Platform 4.8, Red Hat will denote all even numbered minor releases (eg 4.8, 4.10, 4.12) as Extended Update Support (EUS) releases.

For an EUS release, the aforementioned Full and Maintenance support phases are applied with the same conditions to trigger the start and end date for each phase of a release. OpenShift Container Platform EUS releases provides an easier upgrade between EUS releases, permitting them to streamline upgrades of worker nodes and formulate upgrade strategies of EUS to EUS OpenShift releases that will cause less reboots of nodes.

Commencing with OpenShift Container Platform 4.12, Red Hat will additionally include a six month Extended Update Support (EUS) phase for all EUS releases. The EUS phase will follow the maintenance phase for the given release.

Support through the Extended Update Support (EUS) phase is an optional offering for Red Hat OpenShift subscribers. With EUS, Red Hat provides backports of Critical and Important impact security updates and urgent-priority bug fixes for a predefined set of minor releases of Red Hat OpenShift. EUS enables customers to remain with the same minor release of Red Hat OpenShift for a total 24 months, allowing for stable production environments for mission-critical applications.

EUS is provided with x86-64 versions of Red Hat OpenShift Kubernetes Engine, Red Hat OpenShift Container Platform, and Red Hat OpenShift Platform Plus Premium subscriptions. It is also available as an Add-on to x86-64 versions of Red Hat OpenShift Kubernetes Engine, Red Hat OpenShift Container Platform, and Red Hat OpenShift Platform Plus Standard subscriptions. Please contact your Red Hat Sales Representative if you are unsure if you have access to EUS and to help decide if it is appropriate for your environment.

Extended Life Phase

Applicable only for the 4.8 release

During the Extended Life Phase, an OpenShift Container Platform subscription provides continued access to previously released content on the Red Hat Customer Portal, as well as other content such as documentation and the Red Hat Knowledgebase.

For versions of products in the Extended Life Phase, Red Hat will provide limited ongoing technical support. No bug fixes, security fixes, hardware enablement or root-cause analysis will be available during this phase, and support will be provided on existing installations only.

Red Hat reserves the right to terminate the ongoing support in the Extended Life Phase for a particular version of OpenShift Container Platform at any time.

Life Cycle Dates

See footnote [9] for further information on 4.6 EUS end date and footnote [10] for further EUS information.

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:

Red Hat OpenShift Data Foundation

(formerly sold as OpenShift Container Storage)

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

To allow for an increased frequency in developing and delivering features and fixes, OCS maintains a release cadence independent of the OCP minor version release stream. Red Hat aims to forecast these on a 4 month release cadence with OCS, providing customers ample opportunity to plan.

In alignment with OCP, OCS provides three support phases throughout the availability of a minor release; Full Support, Maintenance Support, and Extended Update Support (EUS). The support level throughout each of the life cycle phases is denoted as part of the OpenShift v4 life cycle.

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

Support Phase Boundaries

Full Support

For OpenShift Container Storage 4.7 release or greater
Full Support phase begins at the GA release of the OCS minor version and ends after a 6 month period OR 90 days after the GA of the superseding minor release, whichever is later.

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 OCS to the most current supported micro (4.y.z) version.

Maintenance Support

For OpenShift Container Storage 4.7 release or greater
This phase commences after the Full Support phase for the respective GA and has a duration of 12 months. For instances where the full support phase for the version is beyond 6 months, the duration of the maintenance phase is reduced so the accumulated Full and Maintenance support phases for a release are 18 months.

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.

Extended Update Support

Commencing with OCS 4.8, Red Hat will denote all even numbered minor releases (eg 4.8, 4.10, 4.12) as Extended Update Support (EUS) releases.

For an EUS release, the aforementioned Full and Maintenance support phases are applied with the same conditions to trigger the start and end date for each phase of a release. Customers can therefore expect 18 months of support in total for a release, consistent with non-EUS releases. OpenShift Container Platform EUS releases introduce an easier upgrade between EUS releases, permitting them to streamline upgrades of worker nodes and formulate upgrade strategies of EUS to EUS OpenShift releases that will cause fewer reboots of nodes.

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

Red Hat OpenShift support for Windows Containers

Commencing as part of OpenShift 4.6, Red Hat OpenShift support for Windows Containers is provided and available as an optional, installable component. Red Hat OpenShift support for Windows Containers is not part of the OpenShift Container Platform subscription, it requires a separate subscription and is supported per the Red Hat production terms of support^[5&6].

To allow for an increased frequency in features and fixes, Red Hat OpenShift support for Windows Containers maintains a release cadence independent to the OpenShift Container Platform minor version release stream. Red Hat forecasts Red Hat OpenShift support for Windows Containers to release at a 3 month cadence, at GA or shortly trailing GA of an OpenShift minor release.

Red Hat OpenShift support for Windows Containers 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 an Red Hat OpenShift support for Windows Containers major release is only available for a single, specific minor version of OpenShift Container Platform, as denoted in the life cycle table below. The availability of support on any level for Red Hat OpenShift support for Windows Containers is subject to the overarching version of OpenShift for which it is released, no support is offered for Red Hat OpenShift support for Windows Containers or OpenShift beyond the maintenance or EUS phase boundary for OpenShift.

Support Phase Boundaries

The Red Hat OpenShift support for Windows Containers Full Support Phase commences at the GA release date of the major version and ends on the GA of the superseding major Red Hat OpenShift support for Windows Containers release.

Maintenance Support Phase begins at GA for the superseding major version of Red Hat OpenShift support for Windows Containers and ends on the same date for the corresponding release of OpenShift Container Platform.

Extended Update Support will be available for select Red Hat OpenShift support for Windows Containers 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 Red Hat OpenShift support for Windows Containers for the period in which EUS is available for an OpenShift release.

OpenShift Virtualization

Commencing with OpenShift 4.5, OpenShift Virtualization is provided and available as an optional, installable component, enabling customers to deploy and manage traditional workloads running on virtual machines and next generation workloads running on containers. Comprising of the upstream project kubevirt, OpenShift Virtualization is shipped inclusive as part of the OpenShift Container Platform subscription^[7].

OpenShift Virtualization releases are aimed to be aligned with the OpenShift minor version release cadence. Red Hat aims to forecast OpenShift Virtualization releases at a 4 months cadence, providing customers with ample opportunity to plan for upgrades.

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

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

Note: To maintain supportability of your environment and to take advantage of the new features and bug fixes, you need to use the OpenShift Virtualization release that is compatible with your OpenShift version (as per the table below).

Support Phase Boundaries

The OpenShift Virtualization Full Support Phase commences at the GA release date of the minor version and ends 3 months after the GA release date of the superseding minor OpenShift Virtualization release. The 3 months overlapping period permits a customer to remain in the full support phase across two minor releases.

The Maintenance Support Phase begins as soon as the Full Support Phase ends and is valid for 18 months after the GA release date of the minor version.

Extended Update Support will be available for select OpenShift Virtualization releases. These releases will be outlined on this page as and when they are available. Extended Update Support will provide maintenance support coverage for a release of OpenShift Virtualization for the period in which EUS is available for an OpenShift release.

Note: OpenShift Virtualization 2.7 will now be OpenShift Virtualization 4.8. This is to ensure version alignment with the corresponding OpenShift version.

OpenShift Logging

Commencing as part of OpenShift 4.7, Red Hat OpenShift Logging is provided as an installable component, with a distinct release cycle from the core OpenShift Container Platform. OpenShift Logging is an optional, installable component of OpenShift Container Platform, and is supported per the Red Hat production terms of support^[5&6].

To allow for an increased frequency in features and fixes, Red Hat OpenShift Logging maintains a release cadence independent of the OpenShift Container Platform minor version release stream. Openshift Logging minor releases are expected at approximately a 3 month cadence, but may occur more or less frequently depending on the features targeted for each release.

Red Hat OpenShift Logging 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 Logging 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 Logging is in Full Support phase. The availability of support on any level for Logging is subject to the overarching version of OpenShift for which it is released, no support is offered for Logging or OpenShift beyond the maintenance or EUS phase boundary for OpenShift.

Support Phase Boundaries

The OpenShift Logging 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 OpenShift Logging 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 Logging releases. These releases will be outlined on this page as and when they are available. Extended Update Support will provide maintenance support coverage for a release of OpenShift Logging for the period in which EUS is available for an OpenShift release.

network observability

Commencing with OpenShift 4.12 release, network observability is provided and available as an optional, installable component for OpenShift 4.10 and later. Network Observability 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, network observability maintains a release cadence independent of the OpenShift minor version release stream.

Network observability 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 network observability release stream will continually rebase on stable upstream versions of NetObserv. 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 network observability 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 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.

OpenShift Service Mesh Extended Update Support will be available for select releases. These releases will be outlined on this page (denoted ‘X.Y EUS’), 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 releases may be supported for OpenShift EUS. Providing customers the ability to maintain their OpenShift cluster on a fixed version of OpenShift, and continue to consume OpenShift Service Mesh feature releases for the duration of OpenShift EUS. The OpenShift Service Mesh releases supported for OpenShift EUS are denoted in the support matrix.

OpenShift Serverless

Commencing with OpenShift 4.3, OpenShift Serverless (OSS) is available as an optional, installable component. Composed of the upstream project, Knative, OpenShift Serverless is provided 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 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.

In addition, Red Hat will support OpenShift Serverless customers outside of the Full and Maintenance Support phases, providing assistance and guidance with issues they may have with a previous release of OpenShift Serverless. Support outside of the phases listed in the table below is limited, however, as it does not provide any bug fixing, patching, or security vulnerability updates for that older version. All updates to the OpenShift Serverless releases will be provided as part of either a new release or a patch to a release in the Full or Maintenance life cycle phase.

Support Phase Boundaries

The OpenShift Serverless Full Support Phase commences at the GA release date of the minor version and ends on the GA of the superseding minor Serverless release. No feature updates or non-critical bug fixes will be applied to the release after that point. Rather they will be applied to the current minor release.

The OpenShift Serverless Maintenance Support Phase begins as soon as the release exits the Full Support Phase and lasts for one month. This provides time for the customer to update their Serverless version and allows for any critical bug fixes or patches to security vulnerabilities.

Support for OpenShift Serverless on OpenShift Extended Update Support (EUS) versions may be available for select Serverless releases. As part of keeping Serverless supported, customers might need to update to the new EUS tested release of Serverless. When supported, these releases will be outlined on this page, and as part of release notes.

OpenShift Serverless - Support Phase Dates and OpenShift Support Matrix

OpenShift distributed tracing

Commencing with OpenShift 4.3, OpenShift distributed tracing is provided and available as an optional, installable component. OpenShift distributed tracing 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 distributed tracing maintains a release cadence independent of the OpenShift minor version release stream.

OpenShift distributed tracing 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 distributed tracing 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 distributed tracing 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 GitOps

OpenShift GitOps is an optional and installable component on OpenShift which includes the upstream project Argo CD. OpenShift GitOps is shipped inclusive as part of the OpenShift Container Platform subscription and supported per the Red Hat production terms of support.

To allow for an increased frequency in features and fixes, OpenShift GitOps maintains a release cadence independent of the OpenShift minor version release stream while making sure a fully supported release of OpenShift GitOps is available for every new minor release of OpenShift . Red Hat aims to forecast OpenShift GitOps releases at a 3 month cadence, providing customers ample opportunity to plan for upgrades.

OpenShift GitOps 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 Phase Boundaries

The OpenShift GitOps 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 OpenShift GitOps 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.

Supported Versions of OpenShift

Red Hat aims to provide fully supported versions of GitOps on the latest version of OpenShift, the second latest release of OpenShift, and strategically chosen arbitrary additional versions of OpenShift. We do not anticipate being able to support every version of OpenShift. We aspire to provide support for the latest versions and versions that are popular with our users.

OpenShift GitOps - Support Phase Dates and OpenShift Support Matrix

OpenShift Pipelines

OpenShift Pipelines is an optional and installable component on OpenShift which includes the upstream project Tekton components. OpenShift Pipelines is shipped inclusive as part of the OpenShift Container Platform subscription and supported per the Red Hat production terms of support.

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

OpenShift Pipelines 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 Phase Boundaries

The OpenShift Pipelines 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 Pipelines 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.

Supported Versions of OpenShift

Red Hat aims to provide fully supported versions of Pipelines on the latest version of OpenShift, the second latest release of OpenShift, and strategically chosen arbitrary additional versions of OpenShift. (This goal is not fully realized for versions up to 1.7, as depicted in the lifecycle table.) We do not anticipate being able to support every version of OpenShift. We aspire to provide support for the latest versions and versions that are popular with our users.

OpenShift Pipelines - Support Phase Dates and OpenShift Support Matrix

OpenShift Service Binding Operator

OpenShift Service Binding Operator is an optional and installable component on OpenShift which includes the upstream project redhat-developer/service-binding-operator. Service Binding Operator is shipped inclusive as part of the OpenShift Container Platform subscription and supported per the Red Hat production terms of support.

To allow for an increased frequency in features and fixes, Service Binding Operator maintains a release cadence independent of the OpenShift minor version release stream while making sure a fully supported release of Service Binding Operator is available for every new minor release of OpenShift . Red Hat aims to release Service Binding Operator at a 3 month cadence, providing customers ample opportunity to plan for upgrades.

Service Binding Operator 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 Phase Boundaries

The Service Binding Operator 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 Service Binding Operator 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.

Supported Versions of OpenShift

Red Hat aims to provide fully supported versions of Service Binding Operator on the latest version of OpenShift, the second latest release of OpenShift, and strategically chosen arbitrary additional versions of OpenShift. We do not anticipate being able to support every version of OpenShift. We aspire to provide support for the latest versions and versions that are popular with our users.

OpenShift Service Binding Operator - Support Phase Dates and OpenShift Support Matrix

OpenShift Web Terminal Operator

OpenShift Web Terminal Operator is an optional and installable component on OpenShift. OpenShift Web Terminal Operator is shipped inclusive as part of the OpenShift Container Platform subscription and supported per the Red Hat production terms of support.

OpenShift Web Terminal Operator maintains a release cadence independent of the OpenShift minor version release stream, often releasing shortly after OpenShift. Red Hat aims to provide a compatible version of Web Terminal Operator within a month of the release of a new minor or major version of OpenShift.

OpenShift Web Terminal Operator provides two support phases; 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 Phase Boundaries

The OpenShift Web Terminal Operator Full Support Phase commences at the GA release date and ends when the underlying OpenShift version goes into the Maintenance Support phase.

Maintenance Support Phase begins when the underlying OpenShift goes into Maintenance Support and ends when the underlying OpenShift goes out of Maintenance Support.

Supported Versions of OpenShift

Red Hat aims to provide fully supported versions of Web Terminal Operator for each new major or minor release of OpenShift.

OpenShift Web Terminal Operator - Support Phase Dates and OpenShift Support Matrix

OpenShift Dev Spaces / Red Hat CodeReady Workspaces

Red Hat CodeReady Workspaces has been retitled 'OpenShift Dev Spaces'. Dev Spaces is an optional and installable component on OpenShift which includes the upstream project Eclipse Che. Dev Spaces is shipped inclusive as part of the OpenShift Container Platform subscription and supported per the Red Hat production terms of support.

To allow for an increased frequency in features and fixes, Dev Spaces maintains a release cadence independent of the OpenShift minor version release stream while making sure a fully supported release of Dev Spaces is available for every new minor release of OpenShift . Red Hat aims to release Dev Spaces approximately once every 6 weeks, providing customers ample opportunity to plan for upgrades.

Dev Spaces 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 Phase Boundaries

The Dev Spaces Full Support Phase commences at the GA release date of the minor version and ends immediately after the succeeding minor version of Dev Spaces is released.

The Maintenance Support Phase begins immediately after the release of the succeeding Dev Spaces version and ends 3 months later.

Supported Versions of OpenShift

Red Hat aims to provide fully supported versions of Dev Spaces on the latest version of OpenShift, the second latest release of OpenShift, and strategically chosen arbitrary additional versions of OpenShift. We do not anticipate being able to support every version of OpenShift. We aspire to provide support for the latest versions and versions that are popular with our users.

Red Hat OpenShift Dev Spaces - Support Phase Dates Matrix

Helm

Helm is an installed component on OpenShift which includes components from the upstream project https://helm.sh/. Helm is shipped inclusive as part of the OpenShift Container Platform subscription and supported per the Red Hat production terms of support.

Helm support lifecycle follows the lifecycle of the corresponding OpenShift minor version that it is released with.

Full Support: this phase begins at the GA/release of the minor version and lasts until the end of full support period of corresponding OpenShift minor version.

Maintenance Support: this phase begins when the corresponding OpenShift minor version enters maintenance support and lasts until the end of the OpenShift minor version maintenance support period.

OpenShift Application and Cluster Migration Solutions

Commencing with OpenShift 4.2, Cluster Application Migration Tool (CAM), renamed OpenShift Migration Toolkit for Containers (MTC) 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 Toolkit for Containers is 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.

OpenShift Migration Toolkit for Containers (MTC)

The MTC Full Support Phases Commences at the GA release date of the minor version and ends with the release of the next minor version, which starts its Maintenance Phase. The Maintenance Phase of an MTC release ends after the GA of the superseding minor release.

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 MTC aims 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 MTC is subject to the overarching version of OpenShift for which MTC is supported, no support is offered for MTC or OpenShift beyond the supported phase boundary for OpenShift.

The MTC 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.

MTC 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].

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.

Red Hat build of Cryostat

Red Hat build of Cryostat Overview

Red Hat build of Cryostat is a JFR management tool for containerized JVMs on OpenShift. The upstream community project Cryostat is currently led by Red Hat and is released under the Apache License v2.0.

Red Hat builds of Cryostat are made available through the container catalog, and the Cryostat Operator is available to install through Red Hat OperatorHub on OCP.

The following section outlines the scope of support for Cryostat from Red Hat.

Red Hat build of Cryostat Entitlement

Red Hat build of Cryostat support is available under the OpenJDK entitlement. Any customers who have an active OpenJDK entitlement will have support for Red Hat build of Cryostat.

Red Hat build of Cryostat Life Cycle and Support Policy

Red Hat build of Cryostat releases on a six month cadence, are supported for a minimum period of six months and are superseded by subsequent Cryostat releases.

Red Hat build of Cryostat Updates

New Red Hat build of Cryostat releases supersede previous Red Hat build of Cryostat releases. There will be no updates to old releases.

Red Hat build of Cryostat Life Cycle Dates

Mirror registry for OpenShift

Commencing with OpenShift 4.9.17, mirror registry for OpenShift is provided as an optional component supplementing the disconnected installation process. Mirror registry for OpenShift 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, mirror registry for OpenShift maintains a release cadence independent of the OpenShift minor version release stream.

Mirror registry for OpenShift 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 mirror registry for OpenShift release stream will continually rebase on release versions of Red Hat Quay. 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. Customers will be required to upgrade to the latest version of mirror registry for OpenShift to consume fixes.

Support for mirror registry for OpenShift commences with its initial release, and 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’. At the time of release, mirror registry for OpenShift is supported for use with all minor versions of OpenShift Container Platform 4 which are in Full or maintenance support phases.

OpenShift API for Data Protection

Commencing with OpenShift 4.9, OpenShift API for Data Protection (OADP), provides an optional, installable component or set of api’s that customers, partners and or third party vendors can use to assist in the protection of application workload data on OpenShift Container Platform (OCP) clusters. These components will work/function with OCP versions as far back as OCP 4.6.

Composed of the upstream projects; Velero upstream component, the OpenShift API for Data Protection is 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.

The OADP Full Support Phases Commences at the GA release date of the minor version and ends with the release of the next minor version, which starts its Maintenance Phase. The Maintenance Phase of an OADP release ends after the GA of the superseding minor release.

Support Phase Boundaries

To provide constancy OADP aims to support backup and restore capabilities spanning ~4 (X.Y-2/N/X.Y+2) versions of OCP. This allows for customers and partners to effectively backup an application's data and restore it across OCP version boundaries (subject to the availability of the applicable api’s across these versions).

OpenShift sandboxed containers

Commencing with OpenShift 4.10, OpenShift sandboxed containers is provided and available as an optional, installable component, enabling customers to deploy the containers in a kernel isolated runtime environment. Comprising of the upstream project Kata Containers components, OpenShift sandboxed containers is shipped inclusive as part of the OpenShift Container Platform subscription[5,6&7].

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

OpenShift sandboxed containers, starting OSC 1.3.2, is available through a single, rolling stream which is supported throughout the entire life cycle of OpenShift 4. For the duration of Openshift 4 Full Support Phase, the sandboxed containers release stream will continually rebase on stable upstream versions of kata-containers. 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 fixes and qualified patches may be released via periodic updates.

Support for OpenShift sandboxed containers commences with the release of 1.3.2, the rolling stream is maintained with Full Support coverage throughout OpenShift 4 Full Support Phase. During OpenShift 4 Maintenance support phase, support coverage is only provided per OpenShift 4 Maintenance Support definition.

Note: OpenShift sandboxed container 1.2 that was the first version released is now end of life and customers are advised to upgrade to the latest available version of the operator.

Node Maintenance operator for Red Hat OpenShift

Commencing with OpenShift 4.11, the node maintenance operator for Red Hat OpenShift is provided and available as an optional, installable component. The node maintenance operator for Red Hat OpenShift is provided as part of the OpenShift Container Platform subscription^[7] and supported per the Red Hat production terms of support.

The node maintenance operator for Red Hat OpenShift maintains a release cadence independent of, but generally aligned with, the Red Hat OpenShift Container Platform minor version release stream. Red Hat will release node maintenance operator for Red Hat approximately every 4 months.

This release of the node maintenance operator for Red Hat OpenShift is supported throughout the “full” and “maintenance” lifecycle phases of the targeted Red Hat OpenShift release. To continue receiving bug fixes and new features, customers will be required to upgrade to newer versions of the operator. This may mean an OpenShift minor version upgrade is also necessary, to continue receiving node maintenance operator for Red Hat OpenShift updates.

Self Node Remediation operator for Red Hat OpenShift

Commencing with OpenShift 4.11, the self node remediation operator for Red Hat OpenShift is provided and available as an optional, installable component. The self node remediation operator for Red Hat OpenShift is provided as part of the OpenShift Container Platform subscription^[7] and supported per the Red Hat production terms of support.

The self node remediation operator for Red Hat OpenShift maintains a release cadence independent of, but generally aligned with, the Red Hat OpenShift Container Platform minor version release stream. Red Hat will release self node remediation operator for Red Hat approximately every 4 months.

This release of the self node remediation operator for Red Hat OpenShift is supported throughout the “full” and “maintenance” lifecycle phases of the targeted Red Hat OpenShift release. To continue receiving bug fixes and new features, customers will be required to upgrade to newer versions of the operator. This may mean an OpenShift minor version upgrade is also necessary, to continue receiving self node remediation operator for Red Hat OpenShift updates.

Node Health Check operator for Red Hat OpenShift

Commencing with OpenShift 4.11, the node health check operator for Red Hat OpenShift is provided and available as an optional, installable component. The node health check operator for Red Hat OpenShift is provided as part of the OpenShift Container Platform subscription^[7] and supported per the Red Hat production terms of support.

The node health check operator for Red Hat OpenShift maintains a release cadence independent of, but generally aligned with, the Red Hat OpenShift Container Platform minor version release stream. Red Hat will release node health check operator for Red Hat approximately every 4 months.

This release of the node health check operator for Red Hat OpenShift is supported throughout the “full” and “maintenance” lifecycle phases of the targeted Red Hat OpenShift release. To continue receiving bug fixes and new features, customers will be required to upgrade to newer versions of the operator. This may mean an OpenShift minor version upgrade is also necessary, to continue receiving node health check operator for Red Hat OpenShift updates.

Machine Deletion Remediation operator for Red Hat OpenShift

Commencing with OpenShift 4.13, the machine deletion remediation operator for Red Hat OpenShift is provided and available as an optional, installable component. The machine deletion remediation operator for Red Hat OpenShift is provided as part of the OpenShift Container Platform subscription⁷ and supported per the Red Hat production terms of support.

The machine deletion remediation operator for Red Hat OpenShift maintains a release cadence independent of, but generally aligned with, the Red Hat OpenShift Container Platform minor version release stream. Red Hat will release machine deletion remediation operator for Red Hat approximately every 4 months.

This release of the machine deletion remediation operator for Red Hat OpenShift is supported throughout the “full” and “maintenance” lifecycle phases of the targeted Red Hat OpenShift release. To continue receiving bug fixes and new features, customers will be required to upgrade to newer versions of the operator. This may mean an OpenShift minor version upgrade is also necessary, to continue receiving machine deletion remediation operator for Red Hat OpenShift updates.

Fence Agents Remediation operator for Red Hat OpenShift

Commencing with OpenShift 4.13, the fence agents remediation operator for Red Hat OpenShift is provided and available as an optional, installable component. The fence agents remediation operator for Red Hat OpenShift is provided as part of the OpenShift Container Platform subscription⁷ and supported per the Red Hat production terms of support.

The fence agents remediation operator for Red Hat OpenShift maintains a release cadence independent of, but generally aligned with, the Red Hat OpenShift Container Platform minor version release stream. Red Hat will release fence agents remediation operator for Red Hat approximately every 4 months.

This release of the fence agents remediation operator for Red Hat OpenShift is supported throughout the “full” and “maintenance” lifecycle phases of the targeted Red Hat OpenShift release. To continue receiving bug fixes and new features, customers will be required to upgrade to newer versions of the operator. This may mean an OpenShift minor version upgrade is also necessary, to continue receiving fence agents remediation operator for Red Hat OpenShift updates.

Cert-manager operator for Red Hat OpenShift

Commencing as part of OpenShift 4.12, cert-manager Operator for Red Hat OpenShift is provided as an installable component, with a distinct release cycle from the core OpenShift Container Platform. cert-manager Operator for Red Hat OpenShift is an optional, installable component of OpenShift Container Platform, and is supported per the Red Hat production terms of support.

To allow for an increased frequency in features and fixes, cert-manager Operator for Red Hat OpenShift maintains a release cadence independent of the OpenShift Container Platform minor version release stream. cert-manager Operator for Red Hat OpenShift minor releases are expected at approximately a 3 month cadence, but may occur more or less frequently depending on the features targeted for each release.

Cert-manager Operator for Red Hat OpenShift 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 cert-manager Operator for Red Hat OpenShift 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 cert-manager Operator for Red Hat OpenShift is in Full Support phase. The availability of support on any level for the cert-manager Operator for Red Hat OpenShift is subject to the overarching version of OpenShift for which it is released, no support is offered for the cert-manager Operator for Red Hat OpenShift or OpenShift beyond the maintenance or EUS phase boundary for OpenShift.

Support Phase Boundaries

The cert-manager Operator for Red Hat OpenShift Full Support Phase commences at the GA release date of the minor version and ends on the calendar month after the GA of the superseding minor cert-manager Operator for Red Hat OpenShift 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 cert-manager Operator for Red Hat OpenShift releases. These releases will be outlined on this page as and when they are available. Extended Update Support will provide maintenance support coverage for a release of cert-manager Operator for Red Hat OpenShift for the period in which EUS is available for an OpenShift release.

Third-Party Support

Red Hat Support will not fix/patch the certificate issuers including Let’s Encrypt, Self-signed certificates and ACME as Red Hat does not ship these products and technologies. Any third-party software, including any certificate issuers installed, the Red Hat third-party software support policy will apply^[12].

Secondary Scheduler operator for Red Hat OpenShift

Commencing as part of OpenShift 4.10, Secondary Scheduler operator for Red Hat OpenShift is provided and available as an optional, installable component. The Secondary Scheduler operator for Red Hat OpenShift is provided as part of the OpenShift Container Platform subscription^[7] and supported per the Red Hat Production Scope of support.

To allow for an increased frequency in features and fixes, the Secondary Scheduler operator for Red Hat OpenShift maintains a release cadence independent of the OpenShift Container Platform minor version release stream. Red Hat forecasts Secondary Scheduler operator for Red Hat OpenShift releases at an approximate 3-month cadence, trailing the latest upstream Secondary Scheduler version.

Release and support schedule

NMState operator for Red Hat OpenShift

Commencing with OpenShift 4.10, the NMState operator for Red Hat OpenShift is provided and available as an optional, installable component. The 4.10 release mark the first GA release for the NMState operator on bare metal platform only. The NMState operator for Red Hat OpenShift is provided as part of the OpenShift Container Platform subscription^[7] and supported per the Red Hat production terms of support.

The NMState operator for Red Hat OpenShift maintains a release cadence independent of, but generally aligned with, the Red Hat OpenShift Container Platform minor version release stream. Red Hat will release NMState operator for Red Hat approximately every 3 months.

This release of the NMState operator for Red Hat OpenShift is supported throughout the Full and Maintenance lifecycle phases of the targeted Red Hat OpenShift release. To continue receiving bug fixes and new features, customers will be required to upgrade to newer versions of the operator. This may mean an OpenShift minor version upgrade is also necessary, to continue receiving NMState operator for Red Hat OpenShift updates.

Custom Metric Autoscaler operator for Red Hat OpenShift

The Custom Metric Autoscaler operator for Red Hat OpenShift is provided and available as an optional, installable component. The Custom Metric Autoscaler operator for Red Hat OpenShift is provided as part of the OpenShift Container Platform subscription^[7] and supported per the Red Hat production terms of support.

To allow for an increased frequency in features and fixes, the Custom Metric Autoscaler operator for Red Hat OpenShift maintains a release cadence independent of the Red Hat OpenShift Container Platform minor version release stream. Red Hat will release Custom Metric Autoscaler operator for Red Hat approximately every three months, closely tracking the upstream KEDA version.

Each release of Custom Metric Autoscaler operator for Red Hat OpenShift is supported for four months. To continue receiving bug fixes and new features, customers will be required to upgrade to newer versions of the operator. This may mean an OpenShift minor version upgrade is also necessary, to continue receiving Custom Metric Autoscaler operator for Red Hat OpenShift updates.

Release and support schedule

Multi-Cluster Engine

The multicluster engine for Kubernetes (MCE) operator is a software operator that enhances cluster fleet management. The multicluster engine for Kubernetes operator supports Red Hat OpenShift Container Platform and Kubernetes cluster lifecycle management across clouds and data centers.

The multicluster engine for Kubernetes operator provides the tools and capabilities to address common challenges that administrators and site reliability engineers face as they work across a range of environments, including multiple datacenters, private clouds, and public clouds that run Kubernetes clusters.

Support Phase Boundaries

The multicluster engine for Kubernetes release cadence matches the release schedule of Red Hat Advanced Cluster Management (RHACM) and is supported on the Red Hat Openshift license. Full Support Phase commences at the GA release date of the major version and ends on the GA of the superseding major RHACM release.

Maintenance Support Phase begins at GA for the superseding major version of Red Hat Advanced Cluster Management and ends on the same date for the corresponding release of RHACM.

Logical Volume Manager Storage operator

Commencing as part of OpenShift 4.12, logical volume manager storage for Red Hat OpenShift is provided and available as an optional, installable component. Logical volume manager storage for Red Hat OpenShift is provided as part of the OpenShift Container Platform subscription^[7] and supported per the Red Hat Production Scope of support.

Logical Volume Manager Storage operator releases are aimed to be aligned with the OpenShift minor version release cadence. Red Hat aims to forecast logical volume manager storage releases at a 3 month cadence, providing customers with ample opportunity to plan for upgrades.

Support Phase Boundaries

The logical volume manager storage for Red Hat OpenShift Full Support Phase commences at the GA release date of the minor version and ends on the calendar month after the GA of the superseding minor logical volume manager storage for Red Hat OpenShift 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 logical volume manager storage for Red Hat OpenShift releases. These releases will be outlined on this page as and when they are available. Extended Update Support will provide maintenance support coverage for a release of logical volume manager storage for Red Hat OpenShift for the period in which EUS is available for an OpenShift release.

Release and support schedule

Run Once Duration Override operator for Red Hat OpenShift

Commencing with OpenShift 4.13, the run once duration override operator for Red Hat OpenShift is provided and available as an optional, installable component. The run once duration override operator for Red Hat OpenShift is provided as part of the OpenShift Container Platform subscription^[7] and supported per the Red Hat production terms of support.

The run once duration override operator for Red Hat OpenShift maintains a release cadence independent of, but generally aligned with, the Red Hat OpenShift Container Platform minor version release stream. The release cadence for the run once duration override operator for Red Hat OpenShift is dependent upon any code fixes or new features that need to be implemented.

This release of the run once duration override operator for Red Hat OpenShift is supported throughout the “full” and “maintenance” lifecycle phases of the targeted Red Hat OpenShift release. To continue receiving bug fixes and new features, customers will be required to upgrade to newer versions of the operator. This may mean an OpenShift minor version upgrade is also necessary, to continue receiving run once duration override operator for Red Hat OpenShift updates.

Release and support schedule

Kernel Module Management operator for Red Hat OpenShift

Commencing as part of OpenShift 4.12, kernel module management operator for Red Hat OpenShift is provided and available as an optional, installable component. The kernel module management operator for Red Hat OpenShift is provided as part of the OpenShift Container Platform subscription^[7] and supported per the Red Hat Production Scope of support.

To allow for an increased frequency in features and fixes, the kernel module management operator for Red Hat OpenShift maintains a release cadence independent of the OpenShift Container Platform minor version release stream. Red Hat forecasts the kernel module management operator for Red Hat OpenShift releases at an approximate 3-month cadence, trailing the latest upstream kernel module management version.

Support Phase Boundaries

The kernel module management operator for Red Hat OpenShift Full Support Phase commences at the GA release date of the minor version and ends on the calendar month after the GA of the superseding minor kernel module management operator for Red Hat OpenShift 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 kernel module management operator for Red Hat OpenShift releases. These releases will be outlined on this page as and when they are available. Extended Update Support will provide maintenance support coverage for a release of kernel module management operator for Red Hat OpenShift for the period in which EUS is available for an OpenShift release.

Release and support schedule

Compliance Operator for Red Hat OpenShift

Commencing with OpenShift 4.6, the Compliance Operator is available as an optional, installable component. The Compliance Operator is provided as part of the OpenShift Container Platform subscription[7] and supported per the Red Hat Production Scope of support.

The Compliance Operator lets OpenShift Container Platform administrators describe the required compliance state of a cluster and provides them with an overview of gaps and potential ways to remediate them. It is based on the Compliance as Code upstream project.

To allow for an increased frequency in features and fixes, the Compliance Operator for Red Hat OpenShift maintains a release cadence independent of the OpenShift Container Platform minor version release stream. The release cadence for the Compliance Operator is dependent upon any code fixes or new features that need to be implemented.

The Compliance Operator for Red Hat Openshift is available through a single, rolling stream release channel called stable and is supported to use with all minor versions of OpenShift Container Platform 4, which are in Full or Maintenance support phase. Support for the Compliance Operator rolling stream is maintained with Full Support coverage throughout OpenShift 4 Full Support Phase. During OpenShift 4 Maintenance support phase, support coverage is only provided per OpenShift 4 Maintenance Support definition.

File Integrity Operator for Red Hat OpenShift

Commencing with OpenShift 4.6, the File Integrity Operator is available as an optional, installable component. The File Integrity Operator is provided as part of the OpenShift Container Platform subscription[7] and supported per the Red Hat Production Scope of support.

The File Integrity Operator monitors node file systems for changes using Advanced Intrusion Detection Environment (AIDE).

To allow for an increased frequency in features and fixes, the File Integrity Operator for Red Hat OpenShift maintains a release cadence independent of the OpenShift Container Platform minor version release stream. The release cadence for the File Integrity Operator is dependent upon any code fixes or new features that need to be implemented.

The File Integrity Operator for Red Hat Openshift is available through a single, rolling stream release channel called stable and is supported to use with all minor versions of OpenShift Container Platform 4, which are in Full or Maintenance support phase. Support for the File Integrity Operator rolling stream is maintained with Full Support coverage throughout OpenShift 4 Full Support Phase. During OpenShift 4 Maintenance support phase, support coverage is only provided per OpenShift 4 Maintenance Support definition.

Security Profiles Operator for Red Hat OpenShift

Commencing with OpenShift 4.12, the Security Profiles Operator is available as an optional, installable component. The Security Profiles Operator is provided as part of the OpenShift Container Platform subscription[7] and supported per the Red Hat Production Scope of support.

The Security Profiles Operator for Red Hat OpenShift provides a way to define secure computing (seccomp) profiles and SELinux profiles as custom resources, synchronizing profiles to every node in a given namespace.

To allow for an increased frequency in features and fixes, the Security Profiles Operator for Red Hat OpenShift maintains a release cadence independent of the OpenShift Container Platform minor version release stream. The release cadence for the Security Profiles Operator is dependent upon any code fixes or new features that need to be implemented.

The Security Profiles Operator for Red Hat Openshift is available through a single, rolling stream release channel and is supported to use with all minor versions of OpenShift Container Platform 4, which are in Full or Maintenance support phase. Support for the Security Profiles Operator rolling stream is maintained with Full Support coverage throughout OpenShift 4 Full Support Phase. During OpenShift 4 Maintenance support phase, support coverage is only provided per OpenShift 4 Maintenance Support definition.

---

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
9. In order to provide additional overlap with the superseding OpenShift EUS release, OpenShift 4.6 EUS end date is extended to Oct 27, 2022
10. Historical EUS life cycle information is available on the Extended Update Support (EUS) Overview page
11. Technology Preview: https://access.redhat.com/support/offerings/techpreview
12. Third-Party Support: https://access.redhat.com/third-party-software-support