Skip to content
End of Life & Release Schedules
Kubernetes Release Cycle (2026)

Kubernetes Release Cycle (2026)

DodaTech Updated Jun 20, 2026 3 min read

Kubernetes follows a predictable release cadence of three major versions per year (April, August, December), with each version supported for approximately 14 months. The Kubernetes community maintains the three most recent minor versions (N-3) through patch releases, while older versions enter end-of-life status where no further security patches or bug fixes are provided. Understanding the Kubernetes release cycle is important for planning cluster upgrades, maintaining compliance, and avoiding security vulnerabilities in unsupported versions. Cloud providers like EKS, AKS, and GKE extend base support timelines by several months, but the upstream Kubernetes release schedule governs the core lifecycle.

Kubernetes Version Support Table

VersionRelease DateEnd of Life
1.27Apr 2023Jun 2024
1.28Aug 2023Oct 2024
1.29Dec 2023Feb 2025
1.30Apr 2024Jun 2025
1.31Aug 2024Oct 2025
1.32Dec 2024Feb 2026
1.33Est. Apr 2026Est. Jun 2027

Kubernetes Support Policy

The Kubernetes release cycle is managed by the Kubernetes Enhancement Proposal (KEP) process and the Release Team under the CNCF.

  • Release cadence: 3 releases per year (April, August, December).
  • Support window: Approximately 14 months per minor version.
  • Patch support: Only the 3 most recent minor versions (N-3) receive patch releases. Once a version falls outside this window, it reaches end-of-life.
  • Skipping versions: You cannot skip minor versions during upgrades — you must upgrade sequentially or use a supported skip-path documented by the project.

Cloud providers add their own EOL timelines on top of upstream support:

ProviderExtended Support
Amazon EKSStandard support ~14 months + extended support up to 12 additional months
Azure AKS~14 months upstream + ~3-6 months platform support
Google GKE~14 months with Rapid channel; ~12 months additional on Regular/Stable channels

How to Check Your Kubernetes Version 

kubectl version --short

To check the version of your cluster control plane:

kubectl version --short | grep Server

To check the version of every node:

kubectl get nodes -o wide

FAQ

How long is each Kubernetes version supported?
Each minor version receives approximately 14 months of support from its release date. Patch releases are issued for the three most recent minor versions. After that, the version reaches end-of-life and no longer receives security fixes.
Can I skip a Kubernetes version during upgrade?
Minor version upgrades must be sequential — you cannot skip directly from 1.27 to 1.30. You must upgrade 1.27 → 1.28 → 1.29 → 1.30. Some cloud providers offer special skip-path upgrades, but these are provider-specific extensions.
Do cloud providers support EOL Kubernetes versions?
Amazon EKS, Azure AKS, and Google GKE each offer extended support windows beyond upstream EOL. EKS provides up to 12 months of extended support for a fee. AKS and GKE typically offer 3–6 months of additional platform-level support, but upstream security patches stop.
What happens if I run an unsupported Kubernetes version?
Running an end-of-life Kubernetes version means you will not receive security patches for newly discovered vulnerabilities. This exposes your control plane, nodes, and workloads to known CVEs that remain unpatched, which is a significant security risk.
How do I plan my Kubernetes upgrade schedule?
Given the 14-month support window and 3-release cadence, plan upgrades at least twice per year. Staying within N-2 ensures you always have a supported upgrade path. Most organizations target N-1 or N-2 to balance stability with access to new features.

Related Schedules

  • Docker Engine & Desktop Support
  • Python Version EOL Schedule
Previous iOS Version End of Life (2026) Next Docker Engine & Desktop Support (2026)

Built by the developers of DodaTech

Doda Browser, DodaZIP & Durga Antivirus Pro

Home Browse End of Life & Release Schedules