Namespace has warning message: persistent volume not attached to VM

Products

• VMware vSphere Kubernetes Service

Issue/Introduction

• Guest cluster yaml has the volume configuration for containerd. For example:
  
      workers:
      machineDeployments:
      - class: node-pool
        name: work-node
        replicas: #
        variables:
          overrides:
          - name: volumes
            value:
            - capacity: #Gi
              mountPath: /var/lib/containerd
              name: containerd
  
  
• But the event of namespace where the guest cluster stays in shows Warning message the persistent volume is not attached to work node VM.
  
  Kind: VirtualMachine
Type: Warning
Message: persistent volume: <work-node-name>-containerd not attached to VM


• The PVC is attached to work node successfully.

Environment

vSphere Kubernetes Service

Cause

The message "persistent volume not attached to VM" is a Warning-level event, not a fatal failure. It typically appears during the transient state of the disk attachment process, indicating that the system has initiated the mounting operation but has not yet fully synchronized the status between the supervisor and the guest cluster.

Resolution

Due to the reconciliation loop, the controller continuously retries the attachment until the desired state is achieved. Seeing this warning during the initial creation or scaling phase is considered expected behavior.

The afterward message CnsNodeVmAttachment object as Normal with the reason NodeVMAttachSucceeded is the definitive confirmation that the PVC has successfully attached to the guest cluster worker node VM.

Kind: CnsNodeVmAttachment
Type: Normal
Message: ReconcileCnsNodeVMAttachment: Successfully updated entry in CNS for instance with name "work-node-name-containerd" and namespace "namespace".
Reason: NodeVMAttachSucceeded