Which operator(s) is this request for?
Why this matters
In long-running production clusters, completed backup and restore Jobs accumulate silently in Kubernetes, inflating the API server's object count and making cluster audits and dashboards harder to read. Without a built-in cleanup mechanism, teams must write external scripts or cron jobs just to keep their namespaces tidy. Native ttlSecondsAfterFinished support gives platform and database administrators a single, declarative knob to enforce automatic Job cleanup at either the cluster level or per individual backup and restore operation, with no additional tooling required.
Jira: https://perconadev.atlassian.net/browse/K8SPS-722
Community Note
- Please vote on this issue by adding a 👍 reaction to help the community and maintainers prioritize this request
- Please do not leave "+1" or "me too" comments, as they generate noise 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
Which operator(s) is this request for?
Why this matters
In long-running production clusters, completed backup and restore Jobs accumulate silently in Kubernetes, inflating the API server's object count and making cluster audits and dashboards harder to read. Without a built-in cleanup mechanism, teams must write external scripts or cron jobs just to keep their namespaces tidy. Native
ttlSecondsAfterFinishedsupport gives platform and database administrators a single, declarative knob to enforce automatic Job cleanup at either the cluster level or per individual backup and restore operation, with no additional tooling required.Jira: https://perconadev.atlassian.net/browse/K8SPS-722
Community Note