Runtime
Kubernetes (CNCF)
Kubernetes 1.34 reaches end of life on 27 October 2026 — after that date the project ships no further patch releases, bug fixes, or security fixes for the 1.34 line, and clusters still on it must upgrade.
departs 27 Oct 2026
Quick answers
- Is it true that Kubernetes 1.34 reaches end of life on 27 October 2026?
- Yes. Kubernetes (CNCF) has officially announced it, effective 27 Oct 2026. The Kubernetes project maintains each minor release for about 14 months — roughly a year of fixes plus a two-month maintenance tail — and its official releases page lists **Kubernetes 1.34 with an end-of-life date of 27 October 2026**.
- When does it take effect?
- 27 Oct 2026. Verified against the vendor's own announcement.
- What should I use instead?
- Upgrade to a supported minor before 27 October 2026.
What this means for you
The Kubernetes project maintains each minor release for about 14 months — roughly a year of fixes plus a two-month maintenance tail — and its official releases page lists **Kubernetes 1.34 with an end-of-life date of 27 October 2026**. After that date there are no further patch releases for 1.34.x: no bug fixes and, critically, no security patches. A 1.34 cluster keeps running, but any CVE in the control plane, kubelet, or bundled components found after that date goes unfixed on 1.34, so production clusters, managed-cluster node pools pinned to 1.34, and CI/kind/kubeadm setups that hard-code the version become an unpatched security and compliance exposure. Managed Kubernetes providers (GKE, EKS, AKS) set their own channels that broadly track the upstream cadence and will push or force node-pool and control-plane upgrades around this window, often moving you to paid extended support if you stay behind — so the upstream 27 October 2026 date is the one to plan the upgrade against.
Where to go
Upgrade to a supported minor before 27 October 2026. Kubernetes supports the three most recent minors at any time; with 1.37 current, the supported targets are 1.35 (EOL 28 February 2027), 1.36, and 1.37 (EOL 28 October 2027) — moving to 1.37 buys the longest runway. Upgrade one minor at a time (Kubernetes does not support skipping minors in a single control-plane jump), checking the deprecation and API-removal notes for each step, then bump node pools to match. On managed platforms, move the control plane and node pools to a supported version through your provider's upgrade flow. In kubeadm, kind (`kindest/node`), and CI configs, update any pinned `1.34` version string to the target minor and re-test. Review removed/graduated APIs between your current and target versions before cutover.
- Kubernetes 1.37 — latest, supported through 28 October 2027 (longest runway)
- Kubernetes 1.35 or 1.36 — nearer upgrade targets if a smaller version jump is preferred
- Managed providers' extended-support tiers (GKE/EKS/AKS) — paid runway if you cannot upgrade in time
The Kubernetes releases page gives every minor version roughly 14 months of support, and its official support table lists Kubernetes 1.34 with an end-of-life date of 27 October 2026. That is the end of patch releases for the 1.34 line.
What end of life means here
After 27 October 2026 the project ships no further 1.34.x patch releases — no bug fixes and no security fixes. The cluster keeps working, but it stops getting patches, so any vulnerability discovered in the control plane, kubelet, or bundled components after that date remains unfixed on 1.34. For anything production-facing or holding regulated data, that turns the next relevant CVE into an unpatched exposure.
Who needs to act
- Self-managed clusters pinned to 1.34 (kubeadm, kOps, kind).
- Managed-cluster node pools and control planes on 1.34 — GKE, EKS, and AKS track the upstream cadence and will push or force upgrades around this window, often with paid extended support if you stay behind.
- CI pipelines and
kindest/nodeimages that hard-code1.34.
Upgrade path
Kubernetes keeps the three most recent minors supported. With 1.37 current, upgrade to a supported minor — 1.35 (EOL 28 February 2027), 1.36, or 1.37 (EOL 28 October 2027) — before 27 October 2026. Upgrade one minor at a time (the control plane does not support skipping minors in a single jump), review the API removals and deprecations between your current and target versions, then bump node pools to match and re-test.
Entry changelog
- — last reviewed.
- — Entry created from the Kubernetes project's official releases page, which lists 1.34 with an end-of-life date of 27 October 2026 (with 1.35 EOL 28 February 2027 and 1.37 current, EOL 28 October 2027). The date matches our monitored endoflife.date source independently. No inference. detect left empty deliberately: the upstream release page names no concrete container-image string, and a Kubernetes minor version lives in cluster/kubeadm/managed config rather than a repository manifest, so there is no primary-sourced literal to fingerprint without guessing (SOURCING §6 — fingerprints only from the primary source).
Put this countdown in your README
Building on Kubernetes (CNCF)? Drop this badge into a project’s README or docs — it shows the days left and
refreshes on its own every night from this page. 
[](https://lastcall.dev/entries/kubernetes-1-34-end-of-life)Spot an error or a changed date? Tell us and it’s corrected the same night.