FEATURED STORIES
Kubernetes In-Place Pod Resize: Scale a Pod Vertically Without Restarting It
Yes — Kubernetes can change the CPU and memory of a running pod without deleting it and, in most cases, without restarting its containers. The feature is called In-Place Pod Resize (the KEP calls it In-Place Pod Vertical Scaling), it has been stable since Kubernetes 1.35, and on any cluster at 1.33 or later it is already on by default. You trigger it by patching the pod’s resize subresource: kubectl patch pod checkout-7d9f8c6b5-x2lqp –subresource resize –patch \ ‘{“spec”:{“containers”:[{“name”:”app”,”resources”:{“requests”:{“cpu”:”1″},”limits”:{“cpu”:”2″}}}]}}’ The kubelet updates the container’s cgroup, the pod keeps its name, IP, node and in-memory state, and restartCount stays where it was.…
🎙 ON RADAR PODCAST
LATEST STORIES
Kubernetes HPA Scale Down Slowly? How behavior, Stabilization Windows and Tolerance Really Work
CNCF Sandbox vs Incubating vs Graduated: What the Maturity Levels Actually Mean for Your Toolchain
Helm Chart Management: Centralized Repos vs Per-Service Charts (and the Model That Actually Wins)
FreeLens: What It Is, How to Install It, and Whether You Should Trust It (2026)
Kubernetes HPA on Memory: Working Examples, CPU + Memory Combined, and Troubleshooting
Helm Version Constraints Explained: The Tilde `~`, Caret `^` and Other SemVer Tricks