This repository is archived. Please file in-tree vSphere Cloud Provider issues at https://github.com/kubernetes/kubernetes/issues . CSI Driver for vSphere is available at https://github.com/kubernetes/cloud-provider-vsphere
What would you like to be added:
At the moment all PVs go into the kubevols folder on the Datastore.
And in this folder the vmdks are named like kubernetes-dynamic-pvc-0bdf5725-22fb-11e9-b930-005056802165.vmdk
I'd like to be able to:
Configure kubevols folder name to something else
Configure the prefix kubernetes-dynamic of the vmdk name e.g. dev-cluster-pvc-0bdf5725-22fb-11e9-b930-005056802165.vmdk
Also, it would be good to have some identifier in the vmdk name to highlight the container that created the vmdk e.g. dev-cluster-postgres-default-namespace-pvc-0bdf5725-22fb-11e9-b930-005056802165.vmdk
Why is this needed:
We have separate clusters using the same Datastore and all PVs get lumped into the same folder. It's hard to distinguish which vmdks belong to which cluster. Want to identify clusters and containers that are requesting large amounts of disk space.
What would you like to be added: At the moment all PVs go into the
kubevolsfolder on the Datastore. And in this folder the vmdks are named likekubernetes-dynamic-pvc-0bdf5725-22fb-11e9-b930-005056802165.vmdkI'd like to be able to:
kubevolsfolder name to something elsekubernetes-dynamicof the vmdk name e.g.dev-cluster-pvc-0bdf5725-22fb-11e9-b930-005056802165.vmdkdev-cluster-postgres-default-namespace-pvc-0bdf5725-22fb-11e9-b930-005056802165.vmdkWhy is this needed: We have separate clusters using the same Datastore and all PVs get lumped into the same folder. It's hard to distinguish which vmdks belong to which cluster. Want to identify clusters and containers that are requesting large amounts of disk space.