vSphere CSI add-on fails to apply topology labels when node replica count is 1

Products

• VMware Telco Cloud Automation
• VMware Telco Cloud Platform

Issue/Introduction

vSphere CSI add-on fails to apply topology labels when node replica count is 1

Environment

TCA: 3.2

TCP: 5.0

Cause

The vSphere CSI driver fails to update Kubernetes nodes with new topology changes. This occurs because the driver ignores CSINodeTopology objects after their initial SUCCESS state, meaning any later modifications or additions are not synced.

Resolution

Work Around

• Perform a rollout restart on the vsphere-csi-node DaemonSet and ensure all replacement pods are fully operational before proceeding.
  
  kubectl rollout restart daemonset vsphere-csi-node