Resizing a pod with zero downtime

Description:

A new marketing campaign is expected to drive a sharp increase in traffic to your Kubernetes cluster. A legacy third-party pod named myapp in the apps namespace may not have sufficient CPU resources to handle the load. This app is critical to the business and cannot be restarted. You tried to modify it with kubectl edit, but you got the classic error: Forbidden: pod updates may not change fields other than ...

Tasks:

  • Double the current CPU resources for the pod myapp with zero downtime.

Level: Advanced

Estimated duration: 15min

Access: Signup required

Tags: Kubernetes

Scenarios