Red Hat OpenShift End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Red Hat OpenShift versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
Red Hat OpenShift 4.22 is supported until December 31, 2027. The next Red Hat OpenShift version to reach end of life is 4.19, on December 17, 2026. 18 of 22 tracked Red Hat OpenShift versions are past end of life; the most recent to reach it, 4.18, did so on August 25, 2026.
Running an EOL version? Get matched with support options — free ↓| Version | Latest Release | Release Date | EOL Date | Extended Support | Days | Status |
|---|---|---|---|---|---|---|
| 4.1 | 4.1.41 | Jun 4, 2019 | May 5, 2020 | — | 2315 days past EOL | EOL |
| 4.2 | 4.2.36 | Oct 16, 2019 | Jul 13, 2020 | — | 2246 days past EOL | EOL |
| 4.3 | 4.3.40 | Jan 23, 2020 | Oct 27, 2020 | — | 2140 days past EOL | EOL |
| 4.4 | 4.4.33 | May 5, 2020 | Feb 24, 2021 | — | 2020 days past EOL | EOL |
| 4.5 | 4.5.41 | Jul 13, 2020 | Jul 27, 2021 | — | 1867 days past EOL | EOL |
| 4.6 | 4.6.62 | Oct 27, 2020 | Oct 27, 2022 | — | 1410 days past EOL | EOL |
| 4.7 | 4.7.60 | Feb 24, 2021 | Aug 24, 2022 | — | 1474 days past EOL | EOL |
| 4.8 | 4.8.57 | Jul 27, 2021 | Jan 27, 2023 | Apr 27, 2023 Extended support (ended) |
1318 days past EOL | EOL |
| 4.9 | 4.9.59 | Oct 18, 2021 | Apr 18, 2023 | — | 1237 days past EOL | EOL |
| 4.10 | 4.10.67 | Mar 10, 2022 | Sep 10, 2023 | — | 1092 days past EOL | EOL |
| 4.11 | 4.11.59 | Aug 10, 2022 | Feb 10, 2024 | — | 939 days past EOL | EOL |
| 4.12 | 4.12.96 | Jan 17, 2023 | Jul 17, 2024 | Jan 17, 2025 Extended support (ended) |
781 days past EOL | EOL |
| 4.13 | 4.13.70 | May 17, 2023 | Nov 17, 2024 | — | 658 days past EOL | EOL |
| 4.14 | 4.14.71 | Oct 31, 2023 | May 1, 2025 | Oct 31, 2025 Extended support (ended) |
493 days past EOL | EOL |
| 4.15 | 4.15.67 | Feb 27, 2024 | Aug 27, 2025 | — | 375 days past EOL | EOL |
| 4.16 | 4.16.68 | Jun 27, 2024 | Dec 27, 2025 | Jun 27, 2026 Extended support (ended) |
253 days past EOL | EOL |
| 4.17 | 4.17.55 | Oct 1, 2024 | Apr 1, 2026 | — | 158 days past EOL | EOL |
| 4.18 | 4.18.53 | Feb 25, 2025 | Aug 25, 2026 | Feb 25, 2027 Extended support |
12 days past EOL | EOL |
| 4.19 | 4.19.43 | Jun 17, 2025 | Dec 17, 2026 | — | 102 days remaining | Warning |
| 4.20 | 4.20.35 | Oct 21, 2025 | Apr 21, 2027 | Oct 21, 2027 Extended support |
227 days remaining | Active |
| 4.21 | 4.21.30 | Feb 3, 2026 | Aug 3, 2027 | — | 331 days remaining | Active |
| 4.22 | 4.22.9 | Jun 9, 2026 | Dec 31, 2027 | Jun 30, 2028 Extended support |
481 days remaining | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/red-hat-openshift)
Red Hat OpenShift lifecycle status — the real story
OpenShift Container Platform 4 minors ship on a forecast four-month cadence, and each one moves through two phases: Full Support for six months (or 90 days after the next minor's release, whichever is later), then Maintenance Support until 18 months after general availability. Red Hat designates even-numbered minors (4.12, 4.14, 4.16 …) as Extended Update Support releases, which can be extended with optional add-on terms to a maximum of 48 months.
For planning, the two numbers that matter are 18 and 48: an odd-numbered minor is gone a year and a half after it ships regardless of what you bought, and only an even-numbered minor with EUS entitlements can be held for longer.
Verified against the vendor's lifecycle documentation on August 22, 2026.
Red Hat OpenShift release and support pattern
Across the 22 release lines with a published release date, Red Hat OpenShift has shipped a new line roughly every 4 months (median interval). A line typically stays in standard support for about 1.5 years from its release to its standard-support end date.
Of the 22 release lines tracked, 18 are past end of life and 4 are still within support. The newest line, 4.22, was released June 9, 2026. The next scheduled end of life is 4.19 on December 17, 2026 — 101 days from this build. The longest-supported line currently published is 4.22, to December 31, 2027. Upstream also publishes an extended-support phase for 7 lines, shown in the table above.
Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.
What does Red Hat OpenShift end of life mean for your organization?
When a version of Red Hat OpenShift reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL Red Hat OpenShift should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Your options when Red Hat OpenShift reaches end of life
There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.
| Option | Best when | Watch out for |
|---|---|---|
| Move to a supported version | The system will outlive the current version's support window and you can schedule the work | Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits |
| Replace the component | The project is unmaintained, or a better-supported alternative exists | The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem |
| Buy extended support | Migration is genuinely underway but cannot finish before the deadline, or the workload is frozen by certification or a third-party application | A bridge, not a destination — every year purchased is a year the migration still has to happen |
| Document accepted risk | The system is isolated, short-lived, or scheduled for retirement | Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding |
How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.
Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.
Formalizing decisions like this across your estate? Our free EOL policy template is a ready-to-adopt policy with risk tiers, remediation SLAs, and audit mapping — no signup, free to use and share.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Red Hat OpenShift versions. This is a bridge, not a permanent solution — plan your migration in parallel.
Red Hat OpenShift has 18 versions past end of life — security patches have stopped, but CVE disclosures haven't. Extended support past the official date exists for many products in this position — whether it exists for Red Hat OpenShift is exactly what we check. Tell us where to reach you and we'll reply with matched options and pricing guidance — or an honest "no vendor covers this."