Kubernetes v133 Released: In-Place Resource Resize for Vertical Scaling

By /

Listen to this Post

Featured Image
Kubernetes v1.33 introduces a highly anticipated feature—in-place resource resize for vertical scaling, now in beta. This allows dynamic adjustment of CPU and memory resources without pod restarts, improving efficiency and reducing downtime.

Key Features in v1.33

  • In-Place Vertical Pod Scaling (Beta): Adjust CPU/memory limits without pod termination.
  • Stable Features:
  • Job success policy
  • Volume populators
  • Multiple Service CIDRs
  • NFTables backend for kube-proxy
  • Backoff limits per index for Indexed Jobs
  • Topology-aware routing (trafficDistribution: PreferClose)
  • Enhanced Pod topology spread with taint/toleration support

Release Blog: Kubernetes v1.33 Release Notes

You Should Know: How to Use In-Place Resource Resizing

1. Enable Feature Gate

Ensure the `InPlacePodVerticalScaling` feature gate is enabled in your cluster: 

apiVersion: kubeadm.k8s.io/v1beta3
kind: ClusterConfiguration
featureGates:
InPlacePodVerticalScaling: true

2. Update Pod Resources Without Restart

Modify resources in a running pod using kubectl patch: 

kubectl patch pod my-pod --type=merge -p '{"spec":{"containers":[{"name":"my-container","resources":{"requests":{"cpu":"1","memory":"2Gi"},"limits":{"cpu":"2","memory":"4Gi"}}}]}}'

3. Verify Changes

Check updated resources:

kubectl get pod my-pod -o jsonpath='{.spec.containers[bash].resources}'

4. Automate Scaling with Vertical Pod Autoscaler (VPA)

Deploy VPA for auto-scaling:

kubectl apply -f https://github.com/kubernetes/autoscaler/blob/master/vertical-pod-autoscaler/examples/vpa.yaml

What Undercode Say

Kubernetes 1.33’s in-place scaling is a game-changer for high-availability workloads. Combine this with Linux commands for monitoring: 

 Check Kubernetes node resources 
kubectl top nodes

Monitor pod CPU/memory in real-time 
watch -n 1 'kubectl top pods'

Debug resource allocation 
kubectl describe pod my-pod | grep -A 10 "Resources"

For Windows admins, use `kubectl` via WSL2 or PowerShell: 

kubectl get pods --namespace=default

Expected Output:

POD_NAME READY STATUS RESTARTS AGE 
my-pod 1/1 Running 0 5m

Conclusion: Kubernetes 1.33 enhances operational flexibility with zero-downtime scaling. Master these commands to leverage its full potential.

Expected Output:

A fully detailed technical guide on Kubernetes 1.33’s vertical scaling, complete with commands and best practices.

References:

Reported By: Nagavamsi Kubernetes – Hackers Feeds
Extra Hub: Undercode MoN
Basic Verification: Pass ✅

Join Our Cyber World:

💬 Whatsapp | 💬 Telegram

Related Posts: