-
Notifications
You must be signed in to change notification settings - Fork 336
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Naming of dinamically provisioned volumes #1164
Comments
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
/remove-lifecycle rotten |
the same issue |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
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: