vsphere-csi-node pods are in a CrashLoopBackOff state inside post TKC update

Products

• VMware vSphere Kubernetes Service

Issue/Introduction

After updating the TKC from version 1.28 to 1.29, the vsphere-csi-node pods are in a CrashLoopBackOff state.

This can be confirmed by opening an SSH session to the TKC and running the following command: 

kubectl get -n vmware-system-csi all -o wide

Environment

TKC 1.29

Resolution

Restart the CSI deployment on the Supervisor by running command: kubectl rollout restart deployment -n vmware-system-csi vsphere-csi-controller

Log back into the TKC SSH session and confirm the status of the CSI pods are back in a running state.

It may also be required to restart the CSI pods inside the TKC after doing the above.