Explore the key features in Kubernetes 1.36 'Haru' release: Mutating Admission Policies and User Namespaces graduate to stable, Dynamic Resource Allocation gains prioritized fallback scheduling and device taints, and new alpha features bring visibility into device availability and idle PVC usage.

MetalBear

Kubernetes v1.36 'Haru' brings several notable changes across stability tiers. Mutating Admission Policies graduate to stable, offering a declarative CEL-based in-process alternative to mutating webhooks for common operations like sidecar injection. User Namespaces also reach stable, mapping container UIDs to unprivileged host UIDs to limit container escape impact. Dynamic Resource Allocation (DRA) gains a prioritized fallback scheduling mechanism via a new `firstAvailable` field in ResourceClaims, device taints and tolerations move to beta for health signaling on degraded hardware, and a new alpha `ResourcePoolStatusRequest` API provides visibility into device availability. Additionally, a new `unusedSince` field on PersistentVolumeClaimStatus helps identify idle PVCs consuming storage.

New Features We Find Exciting in the Kubernetes 1.36 Release

Features Moving to Stable: Standing in Clear Morning Light #

Features Moving to Beta: Catching the Spring Wind #

Features Moving to Alpha: Distant Views, Coming Into Focus #