An unsupported platform does not receive security fixes. This table collects the versions that are active on 2 October 2026, with the dates published by the projects. Check it again before any decision: the data changes.
Kubernetes
| Version | Latest patch | End of support |
|---|---|---|
| 1.37 | 1.37.1 | 28 October 2027 |
| 1.36 | 1.36.5 | 28 June 2027 |
| 1.35 | 1.35.9 | 28 February 2027 |
| 1.34 | 1.34.12 | 27 October 2026 |
The project maintains the latest three minor versions, with about a year of patches each. A cluster on 1.34 therefore has only a few days of margin. For more detail, see the Kubernetes releases.
Red Hat OpenShift Container Platform
| Version | GA | End of full support | End of maintenance |
|---|---|---|---|
| 4.22 | 9 June 2026 | 31 December 2026 | 31 December 2027 |
| 4.21 | 3 February 2026 | 9 September 2026 | 3 August 2027 |
| 4.20 | 21 October 2025 | 3 May 2026 | 21 April 2027 |
| 4.19 | 17 June 2025 | 21 January 2026 | 17 December 2026 |
Full support lasts about six months, or 90 days after the next minor version; maintenance runs for up to 18 months. Version 4.18 has Extended Update Support (EUS) until 25 February 2027. Sources: Red Hat Product Life Cycles, endoflife.date and the Red Hat update policy.
Ansible and Jenkins
| Product | Version | Notes |
|---|---|---|
| ansible-core | 2.21 (May 2026) | supported until November 2027; Python 3.12-3.14 on the controller |
| ansible-core | 2.20 | supported until May 2027 |
| ansible-core | 2.19 | supported until November 2026 |
| Jenkins LTS | 2.580.1 (30 September 2026) | requires Java 21 or 25 |
Sources: ansible-core and Jenkins LTS.
What to do with this data
- List the versions in use: clusters, Ansible controllers, Jenkins servers, Java runtimes.
- Flag anything that leaves support within the next six months.
- Plan the upgrade with a rehearsal on a twin environment and a rollback plan.
An assessment is designed for exactly this: an inventory and a prioritised list within a few days.