Kubernetes Version Support & End of Life Schedule
Live support status for every Kubernetes release. Know which versions are supported, what's approaching EOL, and when to upgrade.
Kubernetes Version Status Overview
| Version | Status | Release Date | End of Life | Patch Support | Live Badge |
|---|---|---|---|---|---|
| Kubernetes 1.35 | Current (supported) | January 2026 | March 2027 | ~14 months |
|
| Kubernetes 1.34 | Supported (recommended) | September 2025 | November 2026 | ~14 months |
|
| Kubernetes 1.33 | Supported | May 2025 | July 2026 | ~14 months |
|
| Kubernetes 1.32 | Supported (EOL March 2026) | January 2025 | March 2026 | ~14 months |
|
| Kubernetes 1.31 | END OF LIFE | September 2024 | November 2025 | 14 months (ended) |
|
| Kubernetes 1.30 | END OF LIFE | May 2024 | July 2025 | 14 months (ended) |
|
| Kubernetes 1.29 | END OF LIFE | January 2024 | February 2025 | 14 months (ended) |
|
| Kubernetes 1.28 | END OF LIFE | August 2023 | October 2024 | 14 months (ended) |
|
| Kubernetes 1.27 | END OF LIFE | April 2023 | June 2024 | 14 months (ended) |
|
| Kubernetes 1.26 | END OF LIFE | December 2022 | February 2024 | 14 months (ended) |
|
Understanding Kubernetes Release Cycle
Regular Schedule
New minor version every ~4 months (3 releases per year)
Support Window
Each version supported for ~14 months with patches and security fixes
Concurrent Support
Only the latest 3-4 minor versions receive patches at any time
Patch Frequency
Patch releases roughly monthly with bug fixes and security patches
Support Timeline
Lifecycle Timeline
Visual overview of active support and maintenance windows.
Upgrade Paths
Migration guidance between major versions — breaking changes, effort estimates, and tips.
Breaking Changes
- HPA v2beta2 API removed — migrate to autoscaling/v2
- Deprecated kubelet flags removed
- CSI migration now mandatory for in-tree volume plugins
Migration Notes
Relatively smooth upgrade. Main concern is deprecated API removal — run `kubectl deprecations` or kubent before upgrading. CSI migration should already be done if following best practices.
Breaking Changes
- PodSecurityPolicy finally gone — use Pod Security Standards
- Legacy service account token generation disabled
- kubectl apply server-side is now default
Migration Notes
PSP removal was announced years ago but bites teams who delayed migration. Run the PSP migration tool. Server-side apply is generally better but test with any custom controllers.
Breaking Changes
- Dual-stack networking changes may affect single-stack clusters
- Deprecated annotation-based ingress configs removed
- etcd minimum version bumped to 3.5.x
- Node feature discovery API changes
Migration Notes
The latest release with bleeding-edge features. Test thoroughly in staging. Ingress annotation removal affects older NGINX ingress configurations. etcd upgrade may be needed if running older versions.
Version Risk Assessment
Evaluate risk factors before choosing a version for production.
| Version | EOL Risk | CVE Risk | Ecosystem | Cloud Support | Overall | Recommended Action |
|---|---|---|---|---|---|---|
| Kubernetes 1.30 | Critical | High | Degrading | Dropping | Critical | Upgrade immediately — EOL |
| Kubernetes 1.31 | Critical | High | Degrading | Dropping | Critical | Upgrade immediately — EOL |
| Kubernetes 1.32 | High | Medium | Active | Full | High | Plan upgrade — EOL March 2026 |
| Kubernetes 1.33 | Medium | Low | Active | Full | Medium | Stable — upgrade within 6 months |
| Kubernetes 1.34 | Low | Low | Active | Full | Low | Recommended for production |
| Kubernetes 1.35 | None | Low | Growing | Partial | Low | Latest — adopt when cloud support is full |
Risk combines EOL proximity, known CVEs, ecosystem support (operators, tools), and cloud provider availability. K8s has a rapid release cycle — versions EOL after ~14 months. Assessed February 2026.
Kubernetes Version Feature Comparison
Side-by-side feature differences across major versions.
| Feature | 1.31 | 1.32 | 1.33 | 1.34 | 1.35 |
|---|---|---|---|---|---|
| Sidecar Containers | Stable | Stable | Stable | Stable | Stable |
| Gateway API | v1.0 | v1.1 | v1.1 | v1.2 | v1.2 |
| Pod Security Standards | Stable | Stable | Stable | Stable | Stable |
| Contextual Logging | Beta | Beta | Stable | Stable | Stable |
| CEL Admission | Beta | Stable | Stable | Stable | Stable |
| Topology-aware Routing | Beta | Beta | Stable | Stable | Stable |
| In-place Pod Resize | Alpha | Beta | Beta | Stable | Stable |
| User Namespaces | Alpha | Beta | Beta | Beta | Stable |
| Dual-stack Services | Stable | Stable | Stable | Stable | Stable |
| Container Checkpoint | Alpha | Alpha | Beta | Beta | Stable |
Cloud Provider Kubernetes Support
| Provider | Supported Versions | Latest Available | Upgrade Speed | Auto Upgrade |
|---|---|---|---|---|
| Amazon EKS | 1.28, 1.29, 1.30, 1.31, 1.32 | 1.32 | Typically 1-2 versions behind upstream | Optional, configurable maintenance windows |
| Google GKE | 1.29, 1.30, 1.31, 1.32, 1.33 | 1.33 | Often fastest to adopt new versions | Enabled by default, can be disabled |
| Azure AKS | 1.28, 1.29, 1.30, 1.31, 1.32 | 1.32 | Middle ground, reliable rollouts | Auto-upgrade channels available |
Amazon EKS
EKS Extended Support available for older versions (paid)
Google GKE
Rapid channel gets latest versions quickly
Azure AKS
Long Term Support (LTS) versions available
Supported Version Deep-Dive
Kubernetes 1.35: Current
Key Changes & Features
- Gateway API v1.2 with improved load balancing and traffic splitting
- Enhanced sidecar containers with better lifecycle management
- kubectl debug command improvements for better troubleshooting
Upgrade Notes
Kubernetes 1.35 is the latest release with cutting-edge features. Excellent choice for new clusters and those ready to adopt the newest capabilities.
Kubernetes 1.34: Supported
Key Changes & Features
- ValidatingAdmissionPolicy reaches GA for advanced admission control
- Volume group snapshots for consistent multi-volume backups
- Structured logging improvements across core components
Upgrade Notes
Kubernetes 1.34 is the recommended version for production workloads. Stable, well-tested, with excellent ecosystem support.
Kubernetes 1.33: Supported
Key Changes & Features
- In-place pod vertical resize reaches GA for dynamic resource scaling
- Sidecar containers GA with proper lifecycle guarantees
- Improved multi-network support for advanced networking scenarios
Upgrade Notes
Kubernetes 1.33 offers solid stability with mature features. Good choice for production environments prioritizing proven capabilities.
Kubernetes 1.32: Supported (EOL SOON)
Key Changes & Features
- Dynamic Resource Allocation improvements for specialized hardware
- Custom resource field selectors for more efficient queries
- Automatic PVC removal on StatefulSet scale-down
Breaking Changes
- FlowSchema/PriorityLevelConfiguration v1beta3 removed (use v1)
Upgrade Notes
Kubernetes 1.32 approaches EOL in March 2026. Start planning upgrades now to maintain security support.
API Deprecation Timeline
| Deprecated API | Replacement | Affected Resources | Removed In | Status |
|---|---|---|---|---|
| extensions/v1beta1 | apps/v1 | Deployments, DaemonSets, ReplicaSets | 1.22 | Removed |
| networking.k8s.io/v1beta1 Ingress | networking.k8s.io/v1 | Ingress | 1.22 | Removed |
| PodSecurityPolicy | Pod Security admission | PodSecurityPolicy | 1.25 | Removed |
| flowcontrol.apiserver.k8s.io/v1beta3 | flowcontrol.apiserver.k8s.io/v1 | FlowSchema, PriorityLevelConfiguration | 1.32 | Removed |
| autoscaling/v2beta2 | autoscaling/v2 | HorizontalPodAutoscaler | 1.36 | Deprecated |
Kubernetes Upgrade Best Practices
Pre-Upgrade Checklist
Test in staging environment
Never upgrade production directly. Always test the exact upgrade path in a staging cluster first.
Check for deprecated APIs
Use our deprecation checker or kubectl to identify deprecated API usage in your cluster.
Backup etcd and critical data
Take complete backups of etcd and any stateful workloads before starting the upgrade.
Review addon compatibility
Ensure CNI, CSI, ingress controllers, and other addons support the target version.
Plan rollback strategy
Have a tested rollback plan ready in case the upgrade encounters issues.
Common Upgrade Issues
- Deprecated API versions causing resource creation failures
- Custom Resource Definition compatibility issues
- Network policy changes affecting pod communication
- Third-party operator incompatibility with new version
- Node drain issues with PodDisruptionBudgets
Pro Tip
Use kubectl convert to migrate deprecated API versions before upgrading.
Frequently Asked Questions
How long is each Kubernetes version supported?
Which Kubernetes version should I use?
What happens when Kubernetes version reaches end of life?
How often does Kubernetes release new versions?
Does my cloud provider support the latest Kubernetes version?
What are the most common upgrade issues?
Essential Kubernetes Tools for Your Stack
K8s Deprecation Checker
Scan your cluster for deprecated APIs before upgrading.
Version Support Matrix
Interactive matrix of K8s version compatibility.
Upgrade Planner
Get step-by-step K8s upgrade recommendations.
Cloud K8s Tracker
Track EKS, GKE, and AKS version availability.
Helm Checker
Verify Helm chart K8s version compatibility.
Official Sources
- kubernetes.io — Official Kubernetes release documentation and support policy
- Kubernetes GitHub — Official release notes, changelogs, and issue tracking
- endoflife.date — Community-maintained Kubernetes EOL tracking database
Data is refreshed daily from official CNCF sources. Health badges update automatically.