How to automatically remove backup cron pods?

MySQL & MariaDB Percona Operator for MySQL
1

Currently when a backup job completes the pod is left in “Completed” status. In an environment where backups have to be kept for a long time the number of these pods build up and become a pain when using kubectl for other tasks.

Is there any way to have these pods be automatically removed after some time but keep the pxc-backup resource? Potentially by setting “.spec.ttlSecondsAfterFinished” on the job (Automatic Cleanup for Finished Jobs | Kubernetes)

I couldn’t see any way to set that in the operator.

2

@b602fa9c Do you use keep option percona-xtradb-cluster-operator/cr.yaml at main · percona/percona-xtradb-cluster-operator · GitHub in CR?

3

Yes we set keep to 0

4

In this case you disabled it. If you want to keep e.g. last 5 backups you need to set it in 5 and all jobs will be cleaned up as well .

5

I want to keep the backups but not the backup jobs

6

Hi b602fa9c, I am running into the same problem, where failed or succeeded jobs linger. I also have the ‘keep’ option set, but I believe you are right that this is the retention of backups on the storage destination.

Did you ever get an answer on how to solve this problem?

7

No, I’m still looking for a solution to this.

8

+1 on this - ttlSecondsAfterFinished is a good idea

9

@elie_mouawad what would be the best default for this?

10

Hi @Sergey_Pronin, is this feature likely to be implemented? I would suggest 86400 as a default.

11

@b602fa9c We have a task about this issue [K8SPXC-1214] Add option to automatically cleanup jobs and associated pods - Percona JIRA . I included it to the next PXCO release.

1 Like
12

Is this available for use in any version?