I have found and explanation from VMware
https://docs.vmware.com/en/VMware-vSphere/8.0/vsphere-with-tanzu-services-workloads/GUID-8C645717-C473-4E67-8DEE-049B71447B86.html
When deployed, both Harbor and Contour Supervisor Services create vSphere Pods in the vSphere Namespaces created for these services. These vSphere Pods are required by the services to operate.
You cannot deploy vSphere Pods outside of Supervisor Services on a Supervisor running on the VDS networking stack or a three-zone Supervisor. You can only deploy vSphere Pods for generic use on a single-cluster Supervisor deployed with NSX
But I am a little bit confused because in another post I found another poste that since version vSpshere 8.U1 VDS is supported for Supervisor services ,
Prior vSphere 8 Update 1, the Supervisor Services are only available with Supervisor Clusters enabled using VMware NSX-T. With vSphere 8 U1, Supervisor Services are also supported when using the vSphere Distributed Switch networking stack.
Supervisor Service vSphere 7 vSphere 8
| vSAN Data Persistence Platform Services - MinIO, Cloudian and Dell ObjectScale | | |
| Backup & Recovery Service - Velero | | |
| Certificate Management Service - cert-manager | | |
| Cloud Native Registry Service - Harbor | * | |
| Kubernetes Ingress Controller Service - Contour | | |
| External DNS Service - ExternalDNS | | |
| * The embedded Harbor Registry feature is still available and supported on vSphere 7 and onwards. | |