[FEATURE]: Track "ghost" volumes in PowerFlex clusters when deleted through CSI #1526
Labels
needs-triage
Issue requires triage.
type/feature-request
New feature request. This is the default label associated with a feature request issue.
Comments
vikingtoby
added
needs-triage
|
@vikingtoby: Thank you for submitting this issue! The issue is currently awaiting triage. Please make sure you have given us as much context as possible. If the maintainers determine this is a relevant issue, they will remove the needs-triage label and respond appropriately. We want your feedback! If you have any questions or suggestions regarding our contributing process/workflow, please reach out to us at [email protected]. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the solution you'd like
When a k8s cluster using the PowerFlex CSI driver through the CSM Authorization module has the storageClass RetainPolicy set to "Retain" and both the PVC & PV is deleted, the volume is never deleted on the PowerFlex cluster.
I would like a way to track these volumes, perhaps through them in a "ghostVolumes" CRD in the Authorization module or retrievable through an API endpoint.
Right now, I end up with a bunch of volumes that are "ghosts" and I have to match the volumes in the k8s cluster and the PowerFlex cluster to find which ones I can clean up.
The text was updated successfully, but these errors were encountered: