Proposed title of this feature request

vSphere CSI driver creates tags, tag categories and storage policies with random names
What is the nature and description of the request?

The request from my customer is:

Our Container Hosting Platform is running on a vSphere platform (IAAS). This is a managed service where we don't have many permissions in vCenter as it's not supposed to be exposed to customers. We have to do everything through the API of vRA. As an exception the vSphere CSI driver has the correct permissions to function properly.

Now the IAAS team noticed the vSphere CSI driver is creating a lot of tags, tag categories and storage policies in vCenter. They ask if it is possible to change this behaviour or maybe adjust the naming policy a bit. For storage policies it is understandable this probably can't be changed easily. But we wonder if it is needed for tags, especially tag categories. This creates a lot of overhead. Team IAAS uses tags a lot, also for showback of costs for all the customers. They find this very messy and it requires extra filtering in all of their reports. To be clear, the vSphere environment is not dedicated for Container Hosting. We are one of many customers.

Why does the customer need this? (List the business requirements here)

The number of categories and tags is causing my customer's storage team some issues, this request is to see if this can be tidied up or not. We appreciate that the tags might be a problem but can we cut down on the amount of categories?

List any affected packages or components.

ODF 4.10.5 on OCP 4.10.25

Platform: VMware using Vsan