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.

OpenShift Container Platform v3

This life cycle encompasses stated time periods for each major version of OpenShift. The life cycle for each major version of OpenShift is split into production phases, each identifying the various levels of maintenance over a period of time from the initial release date. The production phases reference a major version of the product, though multiple minor (X.Y) versions of the product may be supported at the same time.

Phase 1 Full Support (5 years) Phase 2 Maintenance Support (2 years) Phase 3 Extended Life Phase (2 years)
Year 1 Year 2 Year 3 Year 4 Year 5 Year 6 Year 7 Year 8 Year 9
OCP Phases

Life Cycle Phases

Full Support

Full support is provided according to the published Scope of Coverage and Service Level Agreement[5&6]. 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 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 are expected to upgrade their OpenShift environment to the most current supported version. On request, and at Red Hat’s discretion, qualified Critical Security errata advisories (RHSAs) and Critical Bug Fix errata advisories (RHBAs) may be made available to non-current minor versions.

Non-current releases within the full support phase which are no longer eligible for maintenance updates of any kind are marked as unmaintained. The following tables outlines the schedule for which minor versions of OpenShift v3 will no longer be eligible for maintenance updates:

v3.X End of Maintenance Schedule

Nov 2018 Jan 2019 Apr 2019 Jul 2019 Oct 2019 Jun 2022
3.0 & 3.1 3.2 & 3.3 3.4 & 3.5 3.6 & 3.7 3.9 & 3.10 3.11
  • Note: End of minor stream maintenance occurs at the end of the denoted months.
  • Maintenance Support

    Maintenance support is provided according to the published Scope of Coverage and Service Level Agreement[5&6]. Likewise, Development Support is provided according to the published Scope of Coverage and Service Level Agreement. During the maintenance phase, qualified security patches of Critical or Important impact, as well as select mission-critical bug-fix patches, will be released, if and when available.

    No new software certifications or enhancements will be provided while the product is in this phase.

    Extended Life Phase

    As an optionally available add-on to an OCP Subscription, Red Hat offers an Extended Life Phase (ELP) subscription[5&6]. The Extended Life Phase (ELP), is for customers who intend to use OpenShift beyond the post-retirement (Maintenance Support) period. Customers are required to maintain active subscriptions to continue receiving access to all previously released content, documentation, Kbase articles, as well as receive limited technical support., this add-on provides this level of access, as an add-on subscription. During this phase, there are no bug fixes, security fixes, new certifications, hardware enablement, feature enhancements, or root cause analysis available.

    Historical GA/Phase End/EOL Dates

    Red Hat OpenShift Container Platform
    Version GA End of Full Support End of Maintenance Support End of Extended Life Phase (ELP)
    1.X Nov, 2012 Nov, 2014 N/A N/A
    2.X Dec, 2013 Dec, 2016 N/A N/A
    3.X[7] June, 2015 June, 2020[7] June, 2022 June, 2024

    Layered and Dependant Components

    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
    RHEL Software Collections Add-Ons 6 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

    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. OpenShift 3.X for POWER is only supported through the Full Support phase. Maintenance and Extended support phases are not available for the POWER architecture.