Inconsistent disk usage on vSAN and inside Pod

Products

• VMware vSphere Kubernetes Service

Issue/Introduction

The disk usage of a VMDK from vSAN's respective is much higher than the PVC usage in Pod.

Cause

- The vSAN UNMAP is disabled by default.

Resolution

1. Follow the sequence to locate the vSAN object information

PVC - PV - VMDK -vSAN Object

2. Find PVC info

• kubectl_--request-timeout180-get-allpvcpvcmnodes---all-namespaces.txt
• kubectl_get_api_resources.txt
• kubectl_get_cnsnodevmattachmentcnsvolumemetadataspersistentvolumeclaimscnsregistervolumes.txt

3. Find Pod info and log in to it to run 'df -h'

• pods.out

4. Find machine information

• 'kubectl_get_tanzukubernetesclustersclusterswcpclustermachinedeploymentswcpmachinetemplateku[...].txt'

5. Find virtual machine information

• kubectl get virtualmachine

6. Find vmx file

 

7. Find vmdk file location

 

8. Find vSAN object information

 

9. Find vSAN OBJ usage

• localcli vsan debug object list

10. Compare the usage from step#3 and step#10

 

11. Follow the KB to enable vSAN unmap

• Procedure to Enable TRIM/UNMAP