-
Notifications
You must be signed in to change notification settings - Fork 28
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
Ability to schedule a PVC for backup by setting an annotation #72
Comments
Seems like a good idea to me. @rbren do you have any thoughts? |
Yeah this seems like a great idea! We have had other requests to be able to reuse schedules, this would take care of both. Will add it to the backlog. @djjudas21 you're welcome to open a PR as well if you want this in the near-term |
Thanks both. I'm no developer and I have no experience with golang, so I'll sit this one out and wait until it's ready 😀 happy to help with testing etc though |
Great request. The concern from @djjudas21 is actually the same as mine. It should be great if we can config the SnapshotGroup using annotation inside PVC. |
Hey, has there been any movement on this one yet? Thanks! |
Sorry, no movement here. Priority right now is 1.25 support. |
Is your feature request related to a problem? Please describe.
I'm new to Gemini, but it seems good and it's working for me. However I'm finding it a bit inconvenient to manually create
SnapshotGroup
resources, as lots of my apps are installed from Helm charts, and then I have to add theSnapshotGroup
manifest.Describe the solution you'd like
It would be cool if I could set an annotation on a PVC like
Obviously there would need to be some defaults set, like the frequency and retention, so there could be a generic resource like:
There could be one or more SnapshotSchedule included with Gemini, and then it would only require setting a single annotation on a PVC (which can be done via most helm charts). For example, Bitnami charts would support this syntax:
... and then you get backups from day zero 🙂
The text was updated successfully, but these errors were encountered: