EOL.WikiEOL.Wiki
← ← Back to all products

Red Hat OpenShiftEnd of Life (EOL) Dates & Support Status

Active
DevOps & CI/CDLatest Version: 4.22.14Latest Release: Sep 15, 2026

Red Hat OpenShift is an enterprise Kubernetes platform with integrated developer and operational tools.

Support summary

Red Hat OpenShift 4.19 reaches EOL in 81 days. Start upgrade planning and compatibility testing now.

What do EOL and support statuses mean?

Next EOL

Dec 17, 2026

Red Hat OpenShift 4.19 · 81 days left

Supported cycles

4

0 lts

Versions

22

Latest Version

4.22.14

Active Support

1

EOL

18

Lifecycle Timeline

May 17, 2023As of Sep 27, 2026
4.22Active · Dec 31, 2027
4.21Security · Aug 3, 2027
4.20Security · Apr 21, 2027
4.19Security · Dec 17, 2026
4.18EOL · Aug 25, 2026
4.17EOL · Apr 1, 2026
4.16EOL · Dec 27, 2025
4.15EOL · Aug 27, 2025
4.14EOL · May 1, 2025
4.13EOL · Nov 17, 2024
ActiveSecurityEOLHistorical phase unknown

Bars show history up to the snapshot date. Gray intervals lack dated support boundaries; arrows indicate an unannounced EOL date, not a support guarantee.

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
4.22Jun 9, 2026Dec 31, 2026Dec 31, 20274.22.14No
Active
4.21Oct 21, 2025Sep 9, 2026Aug 3, 20274.21.32No
Security
4.20Oct 21, 2025May 3, 2026Apr 21, 20274.20.37No
Security
4.19Jun 17, 2025Jan 21, 2026Dec 17, 20264.19.46No
Security
4.18Feb 25, 2025Sep 17, 2025Aug 25, 20264.18.55No
EOL
4.17Oct 1, 2024May 25, 2025Apr 1, 20264.17.56No
EOL
4.16Jun 27, 2024Jan 1, 2025Dec 27, 20254.16.70No
EOL
4.15Feb 27, 2024Sep 27, 2024Aug 27, 20254.15.68No
EOL
4.14Oct 31, 2023May 27, 2024May 1, 20254.14.73No
EOL
4.13May 17, 2023Jan 31, 2024Nov 17, 20244.13.71No
EOL
4.12Jan 17, 2023Aug 17, 2023Jul 17, 20244.12.98No
EOL
4.11Aug 10, 2022Apr 17, 2023Feb 10, 20244.11.59No
EOL
4.10Mar 10, 2022Nov 10, 2022Sep 10, 20234.10.67No
EOL
4.9Oct 18, 2021Jun 10, 2022Apr 18, 20234.9.59No
EOL
4.8Jul 27, 2021Jan 27, 2022Jan 27, 20234.8.57No
EOL
4.7Feb 24, 2021Oct 27, 2021Aug 24, 20224.7.60No
EOL
4.6Nov 9, 2020Mar 24, 2021Oct 27, 20224.6.62No
EOL
4.5Jul 16, 2020Nov 27, 2020Jul 27, 20214.5.41No
EOL
4.4May 18, 2020Aug 13, 2020Feb 24, 20214.4.33No
EOL
4.3Feb 12, 2020Jun 5, 2020Oct 27, 20204.3.40No
EOL
4.2Oct 29, 2019Feb 23, 2020Jul 13, 20204.2.36No
EOL
4.1Jun 18, 2019Nov 16, 2019May 5, 20204.1.41No
EOL

Data sources

Embed this badge

Red Hat OpenShift end-of-life support status badge

Show Red Hat OpenShift's live support status in your README, docs, or dashboard. The badge is a static SVG served from eol.wiki and follows the lifecycle data above.

Markdown

[![Red Hat OpenShift end-of-life status](https://eol.wiki/badge/red-hat-openshift.svg)](https://eol.wiki/red-hat-openshift/)

HTML

<a href="https://eol.wiki/red-hat-openshift/"><img src="https://eol.wiki/badge/red-hat-openshift.svg" alt="Red Hat OpenShift end-of-life status" height="20"></a>
All badges & lifecycle API →

Frequently Asked Questions

Which versions of Red Hat OpenShift have reached end of life?
The following Red Hat OpenShift versions have reached end of life and no longer receive security updates: 4.18, 4.17, 4.16, 4.15, 4.14, 4.13, 4.12, 4.11 (and 10 more). It is recommended to upgrade to a supported version.
Is it safe to continue using Red Hat OpenShift 4.18?
Red Hat OpenShift 4.18 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of Red Hat OpenShift?
The latest version of Red Hat OpenShift is 4.22.14, released in the 4.22 release cycle.
How many versions of Red Hat OpenShift are currently supported?
Red Hat OpenShift currently has 4 actively supported version(s): 4.22, 4.21, 4.20, 4.19.
When does Red Hat OpenShift 4.22 reach end of life?
Red Hat OpenShift 4.22 is scheduled to reach end of life on Dec 31, 2027.
What should I do when Red Hat OpenShift reaches end of life?
When a Red Hat OpenShift version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.