TKG 2.0 with vSphere with Tanzu "Nodedraintimeout" in TKC v1alpha3 vCenter Server 8.0 won't take effect

Products

• VMware vSphere ESXi

Issue/Introduction

Symptoms:
Specify nodedraintimeout can still lead to successful cluster creation, but won’t take effect on the nodes.

Cause

TKR resolver webhook excluded nodedraintimeout contract in CAPI Cluster because of the mismatch in its CAPI provider version.

Resolution

Currently there is no resolution.

Workaround:
To workaround this issue, please follow the below steps:

1. Login as root user to supervisor cluster.
2. To  add node draintimeout for worker nodes:

# kubectl edit md <machine-deployment> -n <namespace>

3. Add nodeDrainTimeout value to

machineDeployment.spec.template.spec.nodeDrainTimeout

4. For control plane nodes, you need to get all control plane machines under the kcp.

root@423c492d#########330a37887bb2a [ ~ ]# kubectl get machines -n gctest -l cluster.x-k8s.io/control-plane="",cluster.x-k8s.io/cluster-name=tkc-minimal
NAME                      CLUSTER       NODENAME   PROVIDERID                                       PHASE         AGE   VERSION
tkc-minimal-#####-bm97g   tkc-minimal              vsphere://423cffbf-####-59d4-fbaa-############   Provisioned   10h   v1.22.9+vmware.1

5. Also edit KCP, and add node drain timeout value to

kcp.spec.machineTemplate.nodeDrainTimeout