Red Hat Advanced Cluster Management for Kubernetes Life Cycle Policy

Updated -

Overview

Red Hat has established specific life-cycle policies for Red Hat Advanced Cluster Management for Kubernetes so customers and partners can effectively plan, deploy, and support their infrastructure. Red Hat publishes this life cycle to provide as much transparency as possible and might make exceptions from these policies as conflicts arise.
All released errata will remain accessible to active subscribers across the entire life cycle of a major version.

Details

Customers are expected to upgrade Red Hat Advanced Cluster Management for Kubernetes to the most current supported version of the product in a timely fashion. Bug fixes and features are targeted for the latest versions of the product (Full Support Phase), though some allowance may be given for critical security risk items for the prior release (Maintenance Support Phase). The Red Hat Advanced Cluster Management for Kubernetes Support Life Cycle Phases are described here:

Lifecycle Phases

This life cycle encompasses stated support phases, delimited by the minor releases of Red Hat Advanced Cluster Management for Kubernetes. The life cycle for a new version (for example, 2.0) or for each minor version (for example, 2.1) of Red Hat Advanced Cluster Management for Kubernetes is split into production phases, each identifying the various levels of maintenance over a period of time from the initial release date.

Full Support

This phase begins at the GA/release of the minor version and ends with the GA of the superseding minor release, which is roughly a three month period.

Full support is provided according to the published Scope of Coverage 1 and Service Level Agreement 2. 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 fixes and qualified patches may be released through periodic updates. Customers are expected to upgrade their Red Hat Advanced Cluster Management for Kubernetes environment to the most current supported minor version. On request, and at the discretion of Red Hat, qualified Critical Security errata advisories (RHSAs) and Critical Bug Fix errata advisories (RHBAs) may be made available for non-current minor versions.

Maintenance Support

This phase begins at the GA/release of the superseding minor version and ends when that version transitions into Maintenance support phase, which is roughly a three month period.

During the Maintenance 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. Other bug fixes (RHBA) and enhancement (RHEA) errata advisories may be released, at the discretion of Red Hat, but should not be expected.
At the end of the maintenance support period, no errata or software updates will be provided for the minor release.

Layered and Dependent Components

Red Hat Advanced Cluster Management for Kubernetes provides the flexibility to use or connect to technologies provided by Red Hat, our partners or third party vendors. All dependent technologies may maintain an independent life cycle from Red Hat Advanced Cluster Management for Kubernetes. As a result, it is important that you check with the technology providers to see how that technology is tested, certified and supported.

Lifecycle Dates for Red Hat Advanced Cluster Management for Kubernetes

Version General Availability (Full Support) Beginning of Maintenance Support End of Maintenance Support
2.0 30th July 2020 Release of 2.1 + one month Release of 2.2 + one month
2.1 5 November 2020 Release of 2.2 + one month Release of 2.3 + one month