Explanation:
* Storage
* Resources
When a stateful pod (like Harbor's database) is stuck Pending/ContainerCreating or repeatedly failing to attach
/mount storage, one of the first checks is whether the PVC'sAccess Modesmatch what the workload and backing storage support (for example, ReadWriteOnce vs ReadWriteMany). In Kubernetes, the PVC and PV explicitly showAccess Modes(for example Access Modes: RWO) when you inspect them.
In the vSphere Namespace UI, theStoragetab is where namespace storage is managed and reviewed (including storage policy assignments that back storage classes/PVCs), making it the natural place to validate the storage configuration being consumed by the Harbor database PVC. VMware's VCF documentation directs administrators to navigate to a namespace and use theStoragetab for storage-related settings.
TheResourcestab is the Kubernetes-object oriented view for the namespace, where you can locate the PVC object associated with the failing pod and inspect its properties/YAML (including the requested storage class and access mode intent). Namespace permissions explicitly include the ability to view Kubernetes resources within the namespace, which aligns with checking PVC details there.