Kubernetes 1.33: Change Pod Size Without Restart! (No More Problems!)

#aws #kubernetes #devops #crosscloudx

😅 The Problem Every DevOps Knows

Imagine this: It's midnight, your app has too many users, and your Pods need more CPU and memory. But in Kubernetes, changing resources means:

Delete and restart the Pods (bye-bye, active connections!)
Wait for a rolling update (more waiting time)
Hope there's no downtime (but there's always some)

Until now, changing Pod resources required a restart. But with Kubernetes 1.33, this is no longer true! 🎉

🚀 What's New? Pods That Grow Without Restarting!

Now you can:
✅ Increase/Decrease CPU and memory without restarting
✅ Works with StatefulSets (great for databases!)
✅ Choose if the Pod restarts on errors

Real-life example:

Problem: An API gets 10x more traffic than usual
Old way: Rolling update → 30 seconds of downtime
New way: kubectl patch → 0 downtime

💡 How to Use It? (Easy Code Example 🛠️)

1. Create a Pod with resize policy

apiVersion: v1
kind: Pod
metadata:
  name: scalable-app
spec:
  containers:
  - name: web
    image: nginx
    resources:
      requests:
        cpu: "1"
        memory: "1Gi"
      limits:
        cpu: "2"
        memory: "2Gi"
    resizePolicy:  # The magic is here!
    - resourceName: cpu
      restartPolicy: NotRequired  # No restart if it fails
    - resourceName: memory
      restartPolicy: NotRequired

2. Change resources while running

kubectl patch pod scalable-app -p '{
  "spec": {
    "containers": [{
      "name": "web",
      "resources": {
        "requests": {"cpu": "2", "memory": "2Gi"},
        "limits": {"cpu": "3", "memory": "3Gi"}
      }
    }]
  }
}'