kubernetes-csi/external-provisioner

Naming of dinamically provisioned volumes

migs35323 opened this issue · 3 comments

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 Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

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:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle rotten
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

/remove-lifecycle rotten