MySQL Bugs: #117952: Unable to specify retention policy for MySQL Operator

Bug #117952	Unable to specify retention policy for MySQL Operator
Submitted:	12 Apr 16:20	Modified:	15 Apr 12:36
Reporter:	Arnold Galovics	Email Updates:
Status:	Verified	Impact on me:	None
Category:	MySQL Operator	Severity:	S4 (Feature request)
Version:		OS:	Any
Assigned to:		CPU Architecture:	Any

View
Add Comment
Files
Developer
Edit Submission
View Progress Log
Contributions

Description:
Based on the documentation and the code, MySQL Operator for Kubernetes doesn't have the ability to specify a retention period for keeping the backups.

This could lead to issues like the volume getting full or paying serious Object Storage costs because nothing gets deleted.

The PostgreSQL operator alternatives have this capability easily:
https://cloudnative-pg.io/documentation/1.25/backup_barmanobjectstore/#retention-policies

Probably one of the most common backup strategies people implement is a daily backup. I wanna be able to specify a window (let's say 30 days) for keeping the backups.

How to repeat:
See the description.

Thank you for the feature request.