Kubernetes v1.36: Haru

Lobsters Hottest Products

Summary

Kubernetes v1.36 “Haru” ships 70 enhancements—18 stable, 25 beta, 25 alpha—plus deprecations and removals.

<p><a href="https://lobste.rs/s/wkaiwv/kubernetes_v1_36_haru">Comments</a></p>
Original Article
View Cached Full Text

Cached at: 04/23/26, 12:28 PM

# Kubernetes v1.36: Haru Source: https://kubernetes.io/blog/2026/04/22/kubernetes-v1-36-release/ **Editors:** Chad M. Crowell, Kirti Goyal, Sophia Ugochukwu, Swathi Rao, Utkarsh Umre As with previous releases, Kubernetes v1.36 delivers new stable, beta, and alpha features. The steady cadence of high-quality releases reflects the strength of our development cycle and the vibrant support of our community. This release contains 70 enhancements: 18 have graduated to Stable, 25 enter Beta, and 25 are new in Alpha. There are also [deprecations and removals](https://kubernetes.io/blog/2026/04/22/kubernetes-v1-36-release/#deprecations-removals-and-community-updates); be sure to read about them. ## Release theme and logo Kubernetes v1.36 Haru logo: a hex badge with the title Haru in flowing script beneath v1.36; Mount Fuji rises on the right, its peak lit red with streaks of pale snow, the Japanese calligraphy 晴れに翔け brushed down its slope; a white Kubernetes helm floats in the blue sky to the left among stylised clouds in the ukiyo-e manner; in the foreground stand two cats as paired guardians, a grey-and-white cat on the left and a ginger tabby on the right, each wearing a collar with a small blue Kubernetes helm charm We open 2026 with Kubernetes v1.36, a release that arrives as the season turns and the light shifts on the mountain. ハル (*Haru*) is a Japanese word that carries many meanings; among those we hold closest are 春 (spring), 晴れ (*hare*, clear skies), and 遥か (*haruka*, far-off, distant). A season, a sky, and a horizon. You will find all three in what follows. The logo, created by [avocadoneko / Natsuho Ide](https://x.com/avocadoneko), draws inspiration from [Katsushika Hokusai](https://en.wikipedia.org/wiki/Hokusai)'s [_Thirty-six Views of Mount Fuji_](https://en.wikipedia.org/wiki/Thirty-six_Views_of_Mount_Fuji) (富嶽三十六景, *Fugaku Sanjūrokkei*), the same series that gave the world [_The Great Wave off Kanagawa_](https://en.wikipedia.org/wiki/The_Great_Wave_off_Kanagawa). Our v1.36 logo reimagines one of the series' most celebrated prints, [_Fine Wind, Clear Morning_](https://en.wikipedia.org/wiki/Fine_Wind,_Clear_Morning) (凱風快晴, *Gaifū Kaisei*), also known as Red Fuji (赤富士, *Aka Fuji*): the mountain lit red in a summer dawn, bare of snow after the long thaw. Thirty-six views felt like a fitting number to sit with at v1.36, and a reminder that even Hokusai didn't stop there.¹ Keeping watch over the scene is the Kubernetes helm, set into the sky alongside the mountain. At the foot of Fuji sit Stella (left) and Nacho (right), two cats with the Kubernetes helm on their collars, standing in for the role of [komainu](https://en.wikipedia.org/wiki/Komainu), the paired lion-dog guardians that watch over Japanese shrines. Paired, because nothing is guarded alone. Stella and Nacho stand in for a very much larger set of paws: the SIGs and working groups, the maintainers and reviewers, the people behind docs, blogs, and translations, the release team, first-time contributors taking their first steps, and lifelong contributors returning season after season. Kubernetes v1.36 is, as always, held up by many hands. Brushed across Red Fuji in the logo is the calligraphy 晴れに翔け (*hare ni kake*), "soar into clear skies". It is the first half of a couplet that was too long to fit on the mountain: > **晴れに翔け、未来よ明け** > *hare ni kake, asu yo ake* > "Soar into clear skies; toward tomorrow's sunrise."² That is the wish we carry for this release: to soar into clear skies, for the release itself, for the project, and for everyone who ships it together. The dawn breaking over Red Fuji is not an ending but a passage: this release carries us to the next, and that one to the one after, on toward horizons far beyond what any single view can hold. ¹ The series was so popular that Hokusai added ten more prints, bringing the total to forty-six. ² 未来 means "the future" in its widest sense, not just tomorrow but everything still to come. It is usually read *mirai*; here it takes the informal reading *asu*. ## Spotlight on key updates Kubernetes v1.36 is packed with new features and improvements. Here are a few select updates the Release Team would like to highlight! ### Stable: Fine-grained API authorization On behalf of Kubernetes SIG Auth and SIG Node, we are pleased to announce the graduation of fine-grained `kubelet` API authorization to General Availability (GA) in Kubernetes v1.36! The `KubeletFineGrainedAuthz` feature gate was introduced as an opt-in alpha feature in Kubernetes v1.32, then graduated to beta (enabled by default) in v1.33. Now, the feature is generally available. This feature enables more precise, least-privilege access control over the kubelet's HTTPS API, replacing the need to grant the overly broad **nodes/proxy** permission for common monitoring and observability use cases. This work was done as part of [KEP #2862](https://kep.k8s.io/2862) led by SIG Auth and SIG Node. ### Beta: Resource health status Before the v1.34 release, Kubernetes lacked a native way to report the health of allocated devices, making it difficult to diagnose Pod crashes caused by hardware failures. Building on the initial alpha release in v1.31 which focused on Device Plugins, Kubernetes v1.36 expands this feature by promoting the `allocatedResourcesStatus` field within the `.status` for each Pod (to beta). This field provides a unified health reporting mechanism for all specialized hardware. Users can now run `kubectl describe pod` to determine if a container's crash loop is due to an **Unhealthy** or **Unknown** device status, regardless of whether the hardware was provisioned via traditional plugins or the newer DRA framework. This enhanced visibility allows administrators and automated controllers to quickly identify faulty hardware and streamline the recovery of high-performance workloads. This work was done as part of [KEP #4680](https://kep.k8s.io/4680) led by SIG Node. ### Alpha: Workload Aware Scheduling (WAS) features Previously, the Kubernetes scheduler and job controllers managed pods as independent units, often leading to fragmented scheduling or resource waste for complex, distributed workloads. Kubernetes v1.36 introduces a comprehensive suite of Workload Aware Scheduling (WAS) features in Alpha, natively integrating the Job controller with a revised [Workload](https://kubernetes.io/docs/concepts/workloads/workload-api/) API and a new decoupled PodGroup API, to treat related pods as a single logical entity. Kubernetes v1.35 already supported [gang scheduling](https://kubernetes.io/docs/concepts/scheduling-eviction/gang-scheduling/) by requiring a minimum number of pods to be schedulable before any were bound to nodes. v1.36 goes further with a new PodGroup scheduling cycle that evaluates the entire group atomically—either all pods in the group are bound together, or none are. This work was done across several KEPs (including [#4671](https://kep.k8s.io/4671), [#5547](https://kep.k8s.io/5547), [#5832](https://kep.k8s.io/5832), [#5732](https://kep.k8s.io/5732), and [#5710](https://kep.k8s.io/5710)) led by SIG Scheduling and SIG Apps. ## Features graduating to Stable *This is a selection of some of the improvements that are now stable following the v1.36 release.* ### Volume group snapshots After several cycles in beta, VolumeGroupSnapshot support reaches General Availability (GA) in Kubernetes v1.36. This feature allows you to take crash-consistent snapshots across multiple PersistentVolumeClaims simultaneously. The support for volume group snapshots relies on a set of [extension APIs for group snapshots](https://kubernetes-csi.github.io/docs/group-snapshot-restore-feature.html#volume-group-snapshot-apis). These APIs allow users to take crash-consistent snapshots for a set of volumes. A key aim is to allow you to restore that set of snapshots to new volumes and recover your workload based on a crash-consistent recovery point. This work was done as part of [KEP #3476](https://kep.k8s.io/3476) led by SIG Storage. ### Mutable volume attach limits In Kubernetes v1.36, the *mutable `CSINode` allocatable* feature graduates to stable. This enhancement allows [Container Storage Interface (CSI)](https://kubernetes-csi.github.io/docs/introduction.html) drivers to dynamically update the reported maximum number of volumes that a node can handle. With this update, the `kubelet` can dynamically update a node's volume limits and capacity information. The `kubelet` adjusts these limits based on periodic checks or in response to resource exhaustion errors from the CSI driver, without requiring a component restart. This ensures the Kubernetes scheduler maintains an accurate view of storage availability, preventing pod scheduling failures caused by outdated volume limits. This work was done as part of [KEP #4876](https://kep.k8s.io/4876) led by SIG Storage. ### API for external signing of ServiceAccount tokens In Kubernetes v1.36, the *external ServiceAccount token signer* feature for service accounts graduates to stable, making it possible to offload token signing to an external system while still integrating cleanly with the Kubernetes API. Clusters can now rely on an external JWT signer for issuing projected service account tokens that follow the standard service account token format, including support for extended expiration when needed. This is especially useful for clusters that already rely on external identity or key management systems, allowing Kubernetes to integrate without duplicating key management inside the control plane. The kube-apiserver is wired to discover public keys from the external signer, cache them, and validate tokens it did not sign itself, so existing authentication and authorization flows continue to work as expected. Over the alpha and beta phases, the API and configuration for the external signer plugin, path validation, and OIDC discovery were hardened to handle real-world deployments and rotation patterns safely. With GA in v1.36, external ServiceAccount token signing is now a fully supported option for platforms that centralize identity and signing, simplifying integration with external IAM systems and reducing the need to manage signing keys directly inside the control plane. This work was done as part of [KEP #740](https://kep.k8s.io/740) led by SIG Auth. ### DRA features graduating to Stable Part of the Dynamic Resource Allocation (DRA) ecosystem reaches full production maturity in Kubernetes v1.36 as key governance and selection features graduate to Stable. The transition of *DRA admin access* to GA provides a permanent, secure framework for cluster administrators to access and manage hardware resources globally, while the stabilization of *prioritized lists* ensures that resource selection logic remains consistent and predictable across all cluster environments. Now, organizations can confidently deploy mission-critical hardware automation with the guarantee of long-term API stability and backward compatibility. These features empower users to implement sophisticated resource-sharing policies and administrative overrides that are essential for large-scale GPU clusters and multi-tenant AI platforms, marking the completion of the core architectural foundation for next-generation resource management. This work was done as part of KEPs [#5018](https://kep.k8s.io/5018) and [#4816](https://kep.k8s.io/4816) led by SIG Auth and SIG Scheduling. ### Mutating admission policies Declarative cluster management reaches a new level of sophistication in Kubernetes v1.36 with the graduation of [MutatingAdmissionPolicies](https://kubernetes.io/docs/reference/access-authn-authz/mutating-admission-policy/) to Stable. This milestone provides a native, high-performance alternative to traditional webhooks by allowing administrators to define resource mutations directly in the API server using the Common Expression Language (CEL), fully replacing the need for external infrastructure for many common use cases. Now, cluster operators can modify incoming requests without the latency and operational complexity associated with managing custom admission webhooks. By moving mutation logic into a declarative, versioned policy, organizations can achieve more predictable cluster behavior, reduced network overhead, and a hardened security model with the full guarantee of long-term API stability. This work was done as part of [KEP #3962](https://kep.k8s.io/3962) led by SIG API Machinery. ### Declarative validation of Kubernetes native types with `validation-gen` The development of custom resources reaches a new level of efficiency in Kubernetes v1.36 as *declarative validation* (with `validation-gen`) graduates to Stable. This milestone replaces the manual and often error-prone task of writing complex OpenAPI schemas by allowing developers to define sophisticated validation logic directly within Go struct tags using the Common Expression Language (CEL). Instead of writing custom validation functions, Kubernetes contributors can now define validation rules using IDL marker comments (such as `+k8s:minimum` or `+k8s:enum`) directly within the API type definitions (`types.go`). The `validation-gen` tool parses these comments to automatically generate robust API validation code at compile-time. This reduces maintenance overhead and ensures that API validation remains consistent and synchronized with the source code. This work was done as part of [KEP #5073](https://kep.k8s.io/5073) led by SIG API Machinery. ### Removal of gogo protobuf dependency for Kubernetes API types Security and long-term maintainability for the Kubernetes codebase take a major step forward in Kubernetes v1.36 with the completion of the `gogoprotobuf` removal. This initiative has eliminated a significant dependency on the unmaintained `gogoprotobuf` library, which had become a source of potential security vulnerabilities and a blocker for adopting modern Go language features. Instead of migrating to standard Protobuf generation, which presented compatibility risks for Kubernetes API types, the project opted to fork and internalize the required generation logic within `k8s.io/code-generator`. This approach successfully eliminates the unmaintained runtime dependencies from the Kubernetes dependency graph while preserving existing API behavior and serialization compatibility. For consumers of Kubernetes API Go types, this change reduces technical debt and prevents accidental misuse with standard protobuf libraries. This work was done as part of [KEP #5589](https://kep.k8s.io/5589) led by SIG API Machinery. ### Node log query Previously, Kubernetes required cluster administrators to log into nodes via SSH or implement a client-side reader for debugging issues pertaining to control-plane or worker nodes. While certain issues still require direct node access, issues with the kube-proxy or kubelet can be diagnosed by inspecting their logs. Node logs offer cluster administrators a method to view these logs using the kubelet API and kubectl plugin to simplify troubleshooting without logging into nodes, similar to debugging issues related to a pod or container. This method is operating system agnostic and requires the services or nodes to log to `/var/log`. As this feature reaches GA in Kubernetes 1.36 after thorough performance validation on production workloads, it is enabled by default on the kubelet through the `NodeLogQuery` feature gate. In addition, the `enableSystemLogQuery` kubelet configuration option must also be enabled. This work was done as a part of [KEP #2258](https://kep.k8s.io/2258) led by SIG Windows. ### Support User Namespaces in pods Container isolation and node security reach a major maturity milestone in Kuber

Similar Articles

Haiku R1/beta6 released

Lobsters Hottest

Haiku R1/beta6 has been released, marking the project's 25th anniversary with over two years of development that includes support for Firefox and hardware virtualization via QEMU on x86_64 systems.

Haiku R1/beta6 has been released

Hacker News Top

Haiku R1/beta6, the latest beta version of the Haiku operating system, has been released after a two-year gap, providing updated features and download options.

Hanakai, and Hanami 3.0 in Full Bloom

Lobsters Hottest

The article announces the merger of Hanami, dry, and rom into the Hanakai community, and the release of Hanami 3.0 featuring built-in mailers, i18n, Minitest support, and up to 3x faster performance with fewer allocations.

Show HN: K10s – A Clickable Kubernetes TUI (Go, Bubble Tea)

Hacker News Top

Show HN: k10s 是一个用 Go 和 Bubble Tea 构建的可点击 Kubernetes 终端 UI,作为 k9s 的现代化替代,提供鼠标操作、全局搜索、延迟 informer 以实现即时启动,并内置具备集群上下文感知能力的 AI 助手。