Open GeekYiwen opened 1 year ago
Thanks for opening this issue :+1:. The team will review it shortly.
If this is a bug report, make sure to include clear instructions how on to reproduce the problem with minimal reproducible examples, where possible. If this is a security report, please review our security policy as outlined in SECURITY.md.
If you haven't already, please take a moment to review our project's Code of Conduct document.
This issue is marked as stale due to inactivity. Add a new comment to reactivate it.
This issue is marked as stale due to inactivity. Add a new comment to reactivate it.
This issue is marked as stale due to inactivity. Add a new comment to reactivate it.
I am working on using Kanister automated to create backups for some database applications in my Kubernetes cluster. When doing this I e.g. want to save backups only if they are 14 days or younger. Retaining the backup files in a Cloud Provider is pretty easy, as this is already implemented (I use Google Cloud Storage Buckets). This leaves the issues that in my Kubernetes Cluster I am left with a load of useless actionsets, which will pile up in the future and make a big mess in there. I'd like a solution to where old actionsets automatically get deleted.
A similar feature is implemented by K8-up (another Kubernetes Operator used for backing up data). This is implemented in their
Scheduler
in theprune:
section. https://k8up.io/k8up/2.7/how-tos/schedules.html