On 27 October 2026, Kubernetes 1.34 reached end of life and will receive no further upstream patches. The date that actually matters depends on your platform: 2 December on EKS, 25 January on GKE, 30 November on AKS.
On October 5, 2026, an official Kubernetes blog post documents node swap, generally available since v1.34, with measured gains of up to 3× density on local SSD. Enable it for best-effort workloads and AI agents, but never to mask a memory leak.
Google launched CPU startup boost for GKE in preview, temporarily raising a container’s CPU during initialization and stepping it back to steady state without a restart, built on Kubernetes In-place Pod Resize. Java, Node.js and Python services suffering slow cold starts get up to 2x faster startup without paying for idle CPU headroom.
Moved into maintenance mode on August 27, 2026, Kubernetes 1.34 reaches end of life on October 27, at which point AWS, Azure and Google all bill $0.60 per cluster per hour — $438 a month — to keep patching it. Upgrade before the deadline: the surcharge buys no features, only the survival of an outdated control plane.
GKE Autopilot, EKS Fargate, and AKS Automatic promise serverless Kubernetes with zero ops overhead. In July 2026, for under 20 pods and a team that knows Linux, k3s on a Hetzner VPS at $6/month delivers identical deployments, zero vendor lock-in, and no egress bill surprises.
