Kubernetes · Lifecycle Status

Kubernetes End of Life (EOL) Dates & Support Timeline

Q: What is the end-of-life date for Kubernetes?

The next Kubernetes version reaching EOL is 1.33 on June 28, 2026. See the full table above for all version EOL dates.

Q: When is the Kubernetes support end date?

The next Kubernetes support end date is June 28, 2026, when version 1.33 reaches end of support. Each version has its own support end date — see the table above for every version's date.

Q: What is the latest supported version of Kubernetes?

The latest active version of Kubernetes is 1.36.2. Always verify against the table above as support windows can change.

Q: Does Kubernetes track end-of-life by point release (e.g. Kubernetes 1.36.1, Kubernetes 1.36.2)?

No — Kubernetes end-of-life dates apply to the entire 1.36.x release series, not individual point releases. A point release like Kubernetes 1.36.1 or Kubernetes 1.36.2 shares the same EOL date as Kubernetes 1.36. Security patches stop for the entire 1.36.x line on that date, regardless of which patch version you are running. Check the table above for EOL dates by major version series.

Complete end-of-life dates, support windows, and security status for all Kubernetes versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.

📅 Get reminded before Kubernetes 1.33 reaches EOL on June 28, 2026 — alerts 90, 30 & 7 days out.

Google →

Latest Active

1.36.2

1.36 series

Next EOL

1.33

Jun 28, 2026

Active Versions

of 21 total

EOL Versions

no longer patched

Critical Risk

EOL Risk Score™ How is this calculated? →

EOL Recency

30/40

Attack Surface

30/30 Critical tier

CISA KEV Exposure

20/20 Yes — CISA KEV

Extended Support

0/10 Available

EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build. Methodology →

Release Cycle Timeline

■ EOL ■ Warning ■ Active ┊ Today

All Versions

Version	Latest Release	Release Date	EOL Date	Days	Status
1.16	1.16.15	Sep 18, 2019	Aug 4, 2020	2149 days past EOL	EOL
1.17	1.17.17	Dec 7, 2019	Dec 25, 2020	2006 days past EOL	EOL
1.18	1.18.20	Mar 25, 2020	Jun 18, 2021	1831 days past EOL	EOL
1.19	1.19.16	Aug 26, 2020	Oct 28, 2021	1699 days past EOL	EOL
1.20	1.20.15	Dec 8, 2020	Feb 28, 2022	1576 days past EOL	EOL
1.21	1.21.14	Apr 8, 2021	Jun 28, 2022	1456 days past EOL	EOL
1.22	1.22.17	Aug 4, 2021	Oct 28, 2022	1334 days past EOL	EOL
1.23	1.23.17	Dec 7, 2021	Feb 28, 2023	1211 days past EOL	EOL
1.24	1.24.17	May 3, 2022	Jul 28, 2023	1061 days past EOL	EOL
1.25	1.25.16	Aug 23, 2022	Oct 27, 2023	970 days past EOL	EOL
1.26	1.26.15	Dec 8, 2022	Feb 28, 2024	846 days past EOL	EOL
1.27	1.27.16	Apr 11, 2023	Jun 28, 2024	725 days past EOL	EOL
1.28	1.28.15	Aug 15, 2023	Oct 28, 2024	603 days past EOL	EOL
1.29	1.29.15	Dec 13, 2023	Feb 28, 2025	480 days past EOL	EOL
1.30	1.30.14	Apr 17, 2024	Jun 28, 2025	360 days past EOL	EOL
1.31	1.31.14	Aug 13, 2024	Oct 28, 2025	238 days past EOL	EOL
1.32	1.32.13	Dec 11, 2024	Feb 28, 2026	115 days past EOL	EOL
1.33	1.33.13	Apr 23, 2025	Jun 28, 2026	5 days remaining	Warning
1.34	1.34.9	Aug 27, 2025	Oct 27, 2026	126 days remaining	Warning
1.35	1.35.6	Dec 17, 2025	Feb 28, 2027	250 days remaining	Active
1.36	1.36.2	Apr 22, 2026	Jun 28, 2027	370 days remaining	Active

What does Kubernetes end of life mean for your organization?

When a version of Kubernetes 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 Kubernetes 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.

Extended Support Options

If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Kubernetes versions. This is a bridge, not a permanent solution — plan your migration in parallel.

endoflife.ai

Need Extended Support?

We work with vetted extended support vendors. Tell us what you need and we'll connect you with the right provider.

Frequently Asked Questions

What is the end-of-life date for Kubernetes?

The next Kubernetes version reaching EOL is 1.33 on June 28, 2026. See the full table above for all version EOL dates.

When is the Kubernetes support end date?

The next Kubernetes support end date is June 28, 2026, when version 1.33 reaches end of support. Each version has its own support end date — see the table above for every version's date.

What is the latest supported version of Kubernetes?

The latest active version of Kubernetes is 1.36.2. Always verify against the table above as support windows can change.

What happens when Kubernetes reaches end of life?

When Kubernetes reaches end of life, the vendor stops issuing security patches. Any CVEs disclosed after the EOL date accumulate indefinitely with no patch path — creating an ever-growing attack surface that most vulnerability scanners do not flag.

How do I check if I'm running an EOL version of Kubernetes?

Check your current version against the table above. If your version's EOL date has passed, you are running unsupported software. You can also use the endoflife.ai Stack Scanner to check your entire dependency file at once.

Is there extended support available for EOL Kubernetes versions?

Some vendors offer extended support for EOL software. Contact the original vendor or check with enterprise support providers for options.

Does Kubernetes track end-of-life by point release (e.g. Kubernetes 1.36.1, Kubernetes 1.36.2)?

No — Kubernetes end-of-life dates apply to the entire 1.36.x release series, not individual point releases. A point release like Kubernetes 1.36.1 or Kubernetes 1.36.2 shares the same EOL date as Kubernetes 1.36. Security patches stop for the entire 1.36.x line on that date, regardless of which patch version you are running. Check the table above for EOL dates by major version series.

Deep Dive

Full Guide

Kubernetes End of Life: Version Support Timeline and Risk Scores

→

Related Products

Data from endoflife.date API · endoflife.date · Generated at build time · How we source data →