Kubernetes 1.32 Reaches End of Life: Teams Urged to Upgrade to 1.34 or Later

Kubernetes 1.32 reached end of life on February 28, 2026, ending all security patches, bug fixes, and official support from the Kubernetes project. Organizations still running the version are now exposed to unpatched vulnerabilities and face growing incompatibility with newer ecosystem tooling.

What End of Life Means

Kubernetes follows a roughly four-month release cycle, with each version supported for approximately 14 months after release. Kubernetes 1.32 was released in December 2024 and has received regular patch updates since then. With end of life, no further CVE patches will be issued — meaning any security vulnerabilities discovered in 1.32 from this point forward will remain unpatched. Additionally, cloud providers typically drop support for end-of-life Kubernetes versions within their managed Kubernetes services within a few months of the upstream EOL date.

Upgrade Path

The recommended upgrade target is Kubernetes 1.34 or later. Kubernetes 1.33 and 1.34 are currently supported, with 1.35 "Timbernetes" as the latest stable release and 1.36 expected in April 2026. Organizations should review the release notes for each intermediate version to identify breaking changes: 1.33 removed several deprecated beta APIs, 1.34 changed default behavior for pod security admission, and 1.35 introduced in-place vertical scaling that may require updates to cluster autoscaler configurations.

Common Upgrade Blockers

The most common reason organizations delay Kubernetes upgrades is dependency on deprecated APIs that are removed in newer versions. Kubernetes 1.32 users who haven't already migrated from the deprecated Ingress API to the Gateway API, or from PodSecurityPolicy to Pod Security Admission, will need to complete those migrations as part of the upgrade process. Tools like Pluto and kubent can scan clusters for deprecated API usage and identify the specific workloads that need to be updated before an upgrade can proceed.