Please vote on this issue by adding a :thumbsup: reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Tell us about the feature
Using the operator and the CR example to save backups to a bucket, we noticed the pxc-backup resource (in Kubernetes) is not removing the backup files inside the target bucket once it's deletes.
This is problematic since the retention is not being enforced in full. Not to mention any manual backup also adds objects to the bucket that never gets deleted.
Right now, the solution would be to delegate this deletion to the bucket lifecycle option, but that is problematic for us since there are more objects being stored in the bucket.
As far as I can tell, the operator is using only the Kubernetes resources. Maybe there should be a new job to clean the bucket objects to preserve the current pxc-backup removal while addressing this issue?
Which product(s) is this request for?
PXC, Operators
Tell us about the problem
Clean up backups from S3 and keep pxc-backup objects in sync
Describe alternatives you've considered
Enable retention on S3 side, but that might cause inconsistency with k8s objects
spron-in
commented
3 years ago
Community Note
Tell us about the feature Using the operator and the CR example to save backups to a bucket, we noticed the pxc-backup resource (in Kubernetes) is not removing the backup files inside the target bucket once it's deletes.
This is problematic since the retention is not being enforced in full. Not to mention any manual backup also adds objects to the bucket that never gets deleted.
Right now, the solution would be to delegate this deletion to the bucket lifecycle option, but that is problematic for us since there are more objects being stored in the bucket.
As far as I can tell, the operator is using only the Kubernetes resources. Maybe there should be a new job to clean the bucket objects to preserve the current pxc-backup removal while addressing this issue?
Which product(s) is this request for? PXC, Operators
Tell us about the problem Clean up backups from S3 and keep pxc-backup objects in sync
Describe alternatives you've considered Enable retention on S3 side, but that might cause inconsistency with k8s objects
Additional context None