Red Hat has changed OpenShift’s lifecycle with version 5 of its Kubernetes-based container platform. Every release will get 24 months of standard support, up from 18 so far, and one in every three releases, starting with 5.2, will be an Extended Life Cycle (ELC) release with up to three additional years, five in total. Aubrey Muhlach and Daniel Messer, OpenShift’s marketing and product management leads, explain the change in a post on the Red Hat blog.
OpenShift 5’s new lifecycle in 30 seconds
- Standard support per release goes from 18 to 24 months starting with OpenShift 5.0.
- ELC releases, one in every three starting with 5.2, add up to five years of support.
- ELC releases will always ship between June and September, and they replace EUS.
- Upgrades that skip releases now need only a single reboot, with AI-assisted pre-checks.
The announcement complements the launch of OpenShift 5, centered on the OpenShift Lightspeed agent, zero-trust security and post-quantum cryptography. Here the focus is different, less flashy but highly relevant for anyone running clusters in production: how long you can stay on a given release and how costly it is to move to the next one. Red Hat sums up its priority as platform stability and long-term predictability.
ELC Releases Instead of EUS
In OpenShift 4, companies that wanted to stay longer on a given release relied on Extended Update Support (EUS) releases. OpenShift 5 replaces those with ELC releases, which arrive in one of every three releases starting with 5.2 and add up to three years of extended support on top of the standard two. Red Hat also commits to shipping them every year between June and September, which makes it possible to plan ahead for the jump from one ELC to the next. The post does not yet give specific dates.
The change isn’t limited to the core. Advanced Cluster Management, Quay, OpenShift Data Foundation and OpenShift Virtualization will follow the same lifecycle as the platform, ELC releases included, and Advanced Cluster Security aligns with it starting with 5.0. Other components, such as Logging, GitOps, Pipelines, Service Mesh, observability, the cert-manager operator, or the data protection APIs, will have versions aligned with each ELC. According to Red Hat, a deployment running OpenShift and these add-ons will be able to stay on the same version for up to five years, receiving only security patches and bug fixes.
Upgrades With a Single Reboot
The other half of the announcement is about upgrades. Red Hat is planning jump upgrades between ELC releases in OpenShift 5 that require only a single reboot of the control plane and worker nodes, instead of chaining several intermediate releases. Major, minor and patch upgrades will follow the same in-place procedure as the rest of the releases, including the move from OpenShift 4 to 5, something that until now tended to require more laborious migrations between platform generations.
Before upgrading, an agent connected to a language model will run background checks whenever a new release is available, detect known risks and problem states, and generate an upgrade plan. For those who don’t want to rely on AI, there will also be release-specific pre-checks that work without any models. According to the authors, upgrading the platform should be a regular, predictable process, not a disruptive event.
For systems teams, the change brings OpenShift closer to the long lifecycles already familiar from enterprise Linux distributions, which is especially useful in regulated environments or critical applications that need recertifying with every version change. It also factors into decisions for teams rethinking their virtualization strategy after the changes at VMware and weighing OpenShift Virtualization against other alternatives, a shift covered in our feature on VMware, Broadcom and the “new normal” of virtualization.
Frequently Asked Questions
How much support does each OpenShift 5 release get?
24 months of standard support, up from 18 in OpenShift 4. ELC releases add up to three more years, five in total.
What are ELC releases?
Extended Life Cycle releases that replace EUS. There will be one in every three starting with OpenShift 5.2, always shipped between June and September.
Can you upgrade from OpenShift 4 to 5 without migrating?
Yes. According to Red Hat, the move from 4 to 5 follows the same in-place upgrade procedure as the rest of the releases.
Sources:
This article is also available in Spanish: “OpenShift 5 alarga el soporte: 24 meses por versión y hasta 5 años con ELC,” on revistacloud.com.
