Proposal
Semi related to #1394 since the operator is relying on the Xtrabackup sidecar in a cluster to handle deletions it can at most delete 1-3 backups at a time per DB instance. This can be time consuming if you have many backups to delete especially if they are large.
Instead of using the sidecar of a cluster, which itself can be fragile see #1394, backup deletions should spawn a dedicated Kubernetes Job that handles the cleanup. The operator can then simply monitor the job and handle final cleanup once the job completes.
Use-Case
No response
Is this a feature you are interested in implementing yourself?
No
Anything else?
No response
Proposal
Semi related to #1394 since the operator is relying on the Xtrabackup sidecar in a cluster to handle deletions it can at most delete 1-3 backups at a time per DB instance. This can be time consuming if you have many backups to delete especially if they are large.
Instead of using the sidecar of a cluster, which itself can be fragile see #1394, backup deletions should spawn a dedicated Kubernetes Job that handles the cleanup. The operator can then simply monitor the job and handle final cleanup once the job completes.
Use-Case
No response
Is this a feature you are interested in implementing yourself?
No
Anything else?
No response