Increasing the TKC worker node replicas count doesn't complete successfully

Products

• VMware vSphere Kubernetes Service

Issue/Introduction

• Increasing the TKC worker node replicas count results in no new nodes joining the cluster.
• In vCenter's tasks you see tasks with the status of "The host does not have sufficient CPU resources to satisfy the reservation."
• TKC cluster remains in a False state
  

  kubectl get tkc -n napp-ns-default
  NAME         CONTROL PLANE   WORKER   TKR NAME         AGE    READY   TKR COMPATIBLE   UPDATES AVAILABLE
  <cluster>    3               4        <tkr_version>    1d     False   True       

      
• The newly created nodes have a PHASE of Pending:
  

  kubectl get machines -A
  NAMESPACE   NAME                   CLUSTER      NODENAME       PROVIDERID           PHASE     AGE   VERSION
  lab         <node_name>            <cluster>    <node_name>    vsphere://<UUID>     Running   29m   v1.29.4+vmware.3-fips.1
  lab         <node_name>            <cluster>    <node_name>    vsphere://<UUID>     Running   29m   v1.29.4+vmware.3-fips.1
  lab         <node_name>            <cluster>    <node_name>    vsphere://<UUID>     Pending   29m   v1.29.4+vmware.3-fips.1 

Resolution

If the TKC is using a guaranteed VM class, you may be requesting more resources than are available within the cluster/resource pool where your TKC resides. You will either need to add additional resources to the cluster, modify the resource pool's reservation settings or change your TKC to use a non-guaranteed VM class. For more information, refer to:

• Using VM Classes with TKG Service Clusters