Setting CPU Limit on vSphere Namespace beyond 1000 GHz renders the unit selection to get empty and actual CPU limit be changed

Products

• VMware vSphere Kubernetes Service

Issue/Introduction

• When opening "Edit Limits" on any vSphere Namespace, entering a CPU limit of 1000 GHz and saving it, it will change the CPU limit to "1" with empty unit selection
  
  
  
  
• The above behavior can be observed with any CPU limit beyond 1000 GHz. (For example, 1250 GHz will be formatted as 1,25)

Environment

VMware vCenter 8.0/9.0

vSphere Kubernetes Service

Cause

When setting the limit beyond 1000 MHz (such as 1500 MHz), the system will format the CPU limit as 1.5 GHz next time the "Edit Limits" dialog is opened. This is expected. Similarly, when specifying a limit of 1500 GHz, it will attempt to format this as 1.5 THz. However, the THz unit is not implemented in the vCenter UI and hence the unit selection remains empty and defaults to MHz when saving.

Resolution

Engineering is aware about this issue and will be addressed in a future release.

Workaround

When opening "Edit Limits" window, ensure the correct CPU amount and correct unit is selected prior to saving.