-
Notifications
You must be signed in to change notification settings - Fork 376
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
Automated snapshoting of deleted PVC #1052
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 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
Hi all, I wanted to gather some opinions around the idea of providing an automated snapshoting mechanism when a PVC is being deleted.
Currently, it can be a bit scary to use a storage class with reclaim policy
Delete
because it means that with one wrong manipulation, if the PVC is deleted, the backing data will also be deleted. On the other hand, using aRetain
storage class is a bit cumbersome because PV will stay in the cluster indefinitely, leading to additional costs. As a result, we need to deploy in our clusters our own garbage collection mechanism to delete unused PV after some time.Having an automated snapshot mechanism would allow us to use
Delete
storage classes while still allowing users to keep a backup of their data in case of accidental deletion.Describe the solution you'd like in detail
For the implementation, I was thinking about the following:
snapshot.storage.kubernetes.io/snapshot-before-deletion
)VolumeSnapshotContent
for the created snapshot (and maybe aVolumeSnapshot
in the same namespace too)but any idea is welcome 😄
Describe alternatives you've considered
Currently, we are doing something similar with a custom controller in our clusters but we are creating snapshots in the cloud provider directly. We were thinking about refactoring the controller to use CSI snapshots instead but then we figured that it might be even better to upstream thin in the exetrenal-snapshotter.
Additional context
I'm not sure if this feature would need a KEP but if it does, I can work on this
The text was updated successfully, but these errors were encountered: