-
Notifications
You must be signed in to change notification settings - Fork 78
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
Cronjob for purging backup is not configurable #1278
Comments
@adejanovski - any chance this will be patched in 1.12.x? |
This patch against main / v1.15.0 will add a
Set to false, the cronjob will not be created It probably should have some tests added and might need tweaks if you want to back-port it to 1.12 but it works on 1.14 and 1.15. |
Text of the patch (for those not wanting to dl the file):
|
What happened?
I noticed that in release 1.12, a cronjob that purges Medusa backup has been added. See #1167
It would be great to be able to disable the cronjob creation from K8ssandra CR.
In our use-case, we are handling backup purging in a different way.
Also, most of the cronjob spec fields are hardcoded and it's not possible to change them from configuration.
It would be great to be able to configure the image, cron schedule, etc..
Also, I'm curious about the technical choices behind this implementation.
Instead of creating a cronjob that performs a
kubectl apply
, why not use something likeMedusaBackupSchedule
? This would allow the operator to automatically createMedusaBackupJob
instances according to the defined cron schedule.For purging and sync, we can imagine a new CR
MedusaTaskSchedule
that would createMedusaTask
.This would have avoided the need of managing an additional container and cronjob.
Did you expect to see something different?
I expect to be able to disable this cronjob, and to be able to configure it's spec.
How to reproduce it (as minimally and precisely as possible):
Deploy a k8ssandra cluster with Medusa ebnabled.
Environment
1.12
Insert image tag or Git SHA here
1.29
┆Issue is synchronized with this Jira Story by Unito
┆Issue Number: K8OP-32
The text was updated successfully, but these errors were encountered: