Kubernetes teams struggle to manage PVCs across Helm releases
When operators remove Helm releases, persistent volume claims (PVCs) may remain, leaving unused storage to clean up manually. But deleting a PVC can also put critical data at risk, and the evidence describes uncertainty about how to retain or remove claims consistently. Static provisioning adds another manual cleanup burden for unused volumes.
For kubernetes operators and administrators. Mentioned from Jan 2019 to Oct 2024 on GitHub.
5 different people described this problem in 2 separate discussions.
- Indie fit
- 5.0/10
- Pain
- 5.6/10
- Frequency
- 6.5/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Businesses
- Competition
- Medium
- Build difficulty
- Medium
What people said
Quoted word for word. Follow a link to read the whole discussion.
As a consequence, once the chart is removed (both using helm delete my-release and helm delete --purge my-release) every PVC created is left on the cluster
i have helm releases where i want to ensure the pvcs do not get deleted in case a release is deleted, since they contain critical data. it would be really good for the behaviour to be clear at least
Build brief
See what to build and who will buy it
- 2 product ideas with the smallest useful version and pricing
- 4 places to find your first customers
- 3 more quotes from people who have this problem
- Current workarounds, existing solutions and risks