Resize CPU and Memory assigned to Pod Containers in vSphere Supervisor Workload Clusters

Products

• Tanzu Kubernetes Runtime

Issue/Introduction

A new feature for resizing CPU and MEM for pod containers without recreating the pod was added in upstream Kubernetes version 1.33.

Environment

vSphere Supervisor 8.x

Workload Cluster running on VKR v1.33.1 or higher

Cause

Starting in upstream Kubernetes version 1.33, the status.resize field for a pod has been deprecated and replaced with the following conditions:

• PodResizeInProgress
• PodResizePending

This feature requires Kubernetes CLI (kubectl) version 1.32.0 or higher.

VKR Release Notes

Kubernetes Documentation Resizing Container Resource

Kubernetes CLI (kubectl) Release Notes

Resolution

In vSphere Supervisor 8.x, the default kubectl version is v1.30.x.

As a result, this new feature is unavailable in vSphere Supervisor 8.x by default.

 

If you want to make use of the new feature in upstream Kubernetes version 1.33, you must manually install Kubernetes CLI (kubectl) v1.32.0 or higher in your environment.

Kubernetes (kubectl) CLI Releases Downloads Page