You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem?/Why is this needed
Volumes generated by the csi provisioner (trough a pvc ) get a random name ( prefix-{UUID} )
even tough a persistent volume claim has a custom name or specify a volume name, the csi provisioner ignores it and generates a random UUID.
I have a cluster with hundreds of volumes all named pvc-UUID and it's really hard to maintence or understand what workload the pv is related to...
Describe the solution you'd like in detail
I'd like to request that volumes get a name based of their pvc name or a way to request a pvc with our own name.
Describe alternatives you've considered
maybe it can grab the name from an annotation or label as alternatives? Additional context longhorn/longhorn#5841
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem?/Why is this needed
Volumes generated by the csi provisioner (trough a pvc ) get a random name ( prefix-{UUID} )
even tough a persistent volume claim has a custom name or specify a volume name, the csi provisioner ignores it and generates a random UUID.
I have a cluster with hundreds of volumes all named pvc-UUID and it's really hard to maintence or understand what workload the pv is related to...
Describe the solution you'd like in detail
I'd like to request that volumes get a name based of their pvc name or a way to request a pvc with our own name.
Describe alternatives you've considered
maybe it can grab the name from an annotation or label as alternatives?
Additional context
longhorn/longhorn#5841
The text was updated successfully, but these errors were encountered: