Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
Add option to automatically cleanup jobs and associated pods
General
Escalation
General
Escalation
Description
When using resources PerconaXtraDBClusterBackup and PerconaXtraDBClusterRestore, resulting jobs and pods are never cleaned up, which can lead to kubernetes api pressure. There should be an option in the backup section of PerconaXtraDBCluster resource to add ttlSecondsAfterFinished in the resulting jobs.
Environment
None
Activity
Gerwin van de Steeg October 30, 2024 at 4:25 AM
Any progress on this? With the issue of the jobs periodically failing combined with the jobs sticking around I’ve got 153 jobs sitting there at the moment on our staging system.
$ kubectl get pods | grep xb-cron-mysql-pxc-db-sql- -c
153
Aaditya Dubey March 1, 2023 at 5:06 PM
Hi @Alexandre Barth,
Thank you for the report. Sending the concern to engineering for further review and updates.
When using resources PerconaXtraDBClusterBackup and PerconaXtraDBClusterRestore, resulting jobs and pods are never cleaned up, which can lead to kubernetes api pressure.
There should be an option in the backup section of PerconaXtraDBCluster resource to add ttlSecondsAfterFinished in the resulting jobs.