DevOpsDreams

Listen to this article AI-narrated article - 19 min 42 sec. Prose is preserved; code and diagram cues refer to the examples below. Your browser does not support audio playback. Open the MP3 . Read the narration transcript - Open audio Kubernetes In-Place Pod Resource Updates And Vertical Pod Resize Kubernetes can now resize a running Pod's CPU and memory without replacing it. This deep dive explains the resize API, kubelet behavior, failure states, VPA integration, and production limits. TL;DR Kubernetes in-place Pod resource updates make container CPU and memory requests and limits mutable through the Pod resize subresource. Kubernetes records the requested values as desired state, while kubelet reports the resources actually configured on the existing node. CPU changes can usually avoid restarts; memory changes need deliberate resize policies and remain riskier, especially when decreasing limits. The feature is stable from Kubernetes 1.35, but it does not reschedule an undersi...

Kubernetes 1.36 on Amazon EKS: The Upgrade Changes That Actually Matter Kubernetes 1.36 is available on Amazon EKS. This operator deep dive covers its breaking changes, security and DRA features, upgrade sequence, and bounded rollback path. TL;DR Kubernetes 1.36 reached Amazon EKS on June 2, 2026 and remains in standard support through August 2, 2027. The upgrade permanently disables gitRepo volumes, enforces stricter IP and CIDR validation, deprecates Service externalIPs, changes SELinux volume behavior, and advances user namespaces, device health, and Dynamic Resource Allocation. Treat the control-plane update as the midpoint: inventory live objects, rehearse admission behavior, update add-ons and nodes, replace Fargate Pods, and validate workload SLOs. EKS permits rollback to the previous minor version within seven days, but it does not undo add-on, CRD, workload, or data changes. Kubernetes 1.36 is not one change. It is a control-plane, node, workload, storage, networking, and h...