* VM storage policies are translated into Kubernetes storage classes.
* Developers can access all assigned VM storage policies in the form of storage classes. * Developers cannot manage storage classes.

A user can have permissions on multiple namespaces. The kubectl commands are typically actioned against the current active namespace.
View the list of available namespaces:
kubectl config get-contexts
Change the current active namespace:
kubectl config use-context <namespace>

A dedicated IP range for virtual IPs. The HAProxy VM must be the only owner of this virtual IP range. The range must not overlap with any IP range assigned to any Workload Network owned by any Supervisor Cluster.

Deleting Artifact:
When an artifact is not referenced by any OCI index, you can delete the artifact freely which will delete its manifest and all associated tags.
When an artifact is referenced by an OCI index, you cannot delete it. In order to delete this artifact, you must first delete all OCI indexes referencing this artifact first, remembering that an artifact can be referenced by multiple parents artifacts pushed onto Harbor by different users. So when deleting an OCI index holding 9 children artifacts not referenced by any other index and 1 child artifact referenced by another index, only 9 out of 10 children artifacts will be deleted.
To delete any artifact in the Harbor interface, click on the artifact and select 'Delete' and confirm.
Not Purge: As a vSphere administrator, you can purge the images for a project in the private image registry by request from DevOps engineers. Purging images from the private image registry deletes all references to the images made by pods, but it does not remove the images from the image registry.

This is the textbook answer, I know kubectl does give you some information.