Kubernetes 1.36 Reaches Enhancements Freeze as April Release Takes Shape

The Kubernetes 1.36 release cycle reached its enhancements freeze milestone on February 11, 2026, locking in the set of features and improvements that will ship in the April 2026 release. The freeze marks the transition from feature proposal to implementation and testing, with the release team now focused on stabilizing accepted enhancements.

Key Features Accepted

Among the enhancements that made the freeze are continued improvements to the Gateway API — Kubernetes' intended replacement for the Ingress resource — including expanded support for gRPC routing, TLS passthrough, and cross-namespace references. Windows container support receives several improvements, including better resource management and support for host networking on Windows nodes. The release also advances the deprecation of several legacy networking components as the project continues its multi-release migration to modern networking primitives.

Production Readiness

The production readiness review, which occurred on February 4-5, evaluated each proposed enhancement for operational maturity. Features that passed the review demonstrated adequate monitoring, rollback capabilities, and documentation for production use. Features that failed were either deferred to a future release or accepted at a lower maturity level (alpha or beta) with additional guardrails.

Timeline and Context

Kubernetes 1.36 is expected to reach general availability in mid-April 2026. The release follows Kubernetes 1.35 "Timbernetes," which introduced in-place vertical scaling — the ability to adjust CPU and memory allocations for running pods without restarting them. Meanwhile, Kubernetes 1.32 reached end of life on February 28, meaning organizations still running that version will no longer receive security patches and should prioritize upgrading to 1.34 or later.