OpenShift Dedicated Life Cycle

Overview

Red Hat provides a published product life cycle for Red Hat OpenShift Dedicated in order for customers and partners to effectively plan, deploy, and support their applications running on the platform. Red Hat publishes this life cycle in order to provide as much transparency as possible and may make exceptions from these policies as conflicts may arise.

The lifecycle of Red Hat OpenShift Dedicated follows a release-driven, phased approach where a single, minor version is available and will be supported at any one time.

Red Hat OpenShift Dedicated is a managed instance of Red Hat OpenShift and maintains an independent release schedule. More details about the managed offering can be found in the Service Definition. The availability of Security Advisories and Bug Fix Advisories for a specific version are dependent upon Red Hat OpenShift Container Platform’s life cycle policy and subject to the OpenShift Dedicated maintenance schedule.

Major Versions

Major (e.g. version 3 or version 4) versions of Red Hat OpenShift Dedicated are supported for one year following the release of a subsequent major version or the retirement of the product. Existing customers are allowed to create new clusters with a major version for 6 months following the release of a subsequent major version.

For example, if a version 5 were made available on Red Hat OpenShift Dedicated on 1st of January, version 4 would be allowed to continue running on managed clusters for 12 months, until the 31st of December. After this time clusters would need to be upgraded or migrated to version 5. Additionally, version 4 would continue to be installable by existing customers for 6 months after a version 5 was made available, until the 30th of June.

Minor versions

Support for a minor (4.y) version begins at the OpenShift Dedicated release of the minor version and ends with the availability of an upgrade to the subsequent minor version (roughly a four month period). For example, the minor version 4.1 would be supported from the date it is made available for Red Hat OpenShift Dedicated until version 4.2 is available for upgrade.

During the period in which a minor release is supported, qualified Critical and Important Security Advisories (RHSAs) and Urgent and Selected High Priority Bug Fix Advisories (RHBAs) may be applied to OpenShift Dedicated clusters as they become available; all other available fix and qualified patches are applied via periodic updates.

As newer minor releases become available, Red Hat will automatically deploy the upgrades per a predefined schedule. Notification of minor release upgrades are provided two weeks in advance of installation.

Life Cycle Dates (v4)