What Changed Recently
Apr 23, 2025
1.33: native sidecars and nftables kube-proxy go stable
Aug 27, 2025
1.34: core Dynamic Resource Allocation goes GA
Dec 17, 2025
1.35: in-place Pod resize GA, cgroup v1 off by default, ipvs deprecated
Mar 24, 2026
Ingress NGINX retired
Apr 22, 2026
1.36: MutatingAdmissionPolicy GA, gitRepo volumes disabled, externalIPs deprecated
Aug 26, 2026
1.37: HPA scale to zero in beta, KYAML stable, kube-dns deprecated
31. What is in-place Pod resize?
Graduated to GA in 1.35, per the 1.35 release announcement, it lets you change a running container's CPU and memory requests and limits without recreating the Pod.
Each container's resizePolicy says whether a change needs a container restart; CPU changes usually do not, while memory changes for runtimes that size their heap at startup, such as the JVM, often should.
It matters for stateful and long-warming workloads that used to lose caches or connections on every vertical scale, and it lets VPA apply recommendations without evictions.
If the node lacks room, the resize stays pending rather than moving the Pod.
32. What do the cgroup v1 and containerd 1.x changes mean for a cluster upgrade?
Since 1.35, the kubelet's failCgroupV1 setting defaults to true, so a node still on cgroup v1 fails to start unless an operator sets it back to false as a temporary override.
Memory QoS and some newer resource features work only on cgroup v2, and the project plans to remove v1 support.
1.35 was also the last release to support containerd 1.x; 1.36 and later need containerd 2.0 or newer, and the kubelet_cri_losing_support metric flags nodes at risk.
Both are node-image checks to run before an upgrade, and old self-managed nodes on older Linux distributions are where they bite.
33. Ingress NGINX is retired. What should a team running it do?
Per the retirement announcement, the project stopped releases, bug fixes and security fixes on March 24, 2026. Existing installs keep running and the images remain available, but the next CVE will not be patched.
In March 2025, the IngressNightmare vulnerabilities (CVE-2025-1974 among them) showed how exposed an unpatched ingress controller is.
The plan: inventory Ingress resources and the NGINX-specific annotations they rely on, choose a Gateway API implementation (Envoy Gateway, Istio, Cilium, NGINX Gateway Fabric, a cloud provider's gateway), translate with Ingress2Gateway, then run both side by side and shift DNS.
Alternatively, move to another maintained Ingress controller, and plan Gateway API later.
34. Can the HorizontalPodAutoscaler scale to zero now?
Yes, in beta and enabled by default since 1.37, for HPAs driven by object or external metrics. Setting spec.minReplicas: 0 lets an idle queue consumer or GPU worker scale down to nothing and come back when the metric returns.
It does not work with CPU or memory metrics, because those need running Pods to report anything.
While holding a workload at zero, the HPA sets a ScaledToZero condition, which separates "scaled to zero by the HPA" from "scaled to zero by a person".
Before this, scale to zero meant KEDA or Knative; KEDA still adds the event sources and activation logic that the HPA lacks.
35. What is Dynamic Resource Allocation?
DRA is the API for requesting specialized hardware such as GPUs, network interfaces and accelerators, and its core went GA in 1.34.
Instead of an opaque count like nvidia.com/gpu: 1, a Pod references a ResourceClaim, and vendors publish devices with attributes in ResourceSlices, so a claim can ask for "a GPU with at least 40 GB of memory" and the scheduler matches it.
Later releases added prioritized alternatives, admin access and device taints, several of which went stable in 1.36 and 1.37.
It matters for any team running AI workloads on Kubernetes, where device plugins could not express sharing, partitioning or topology.