Skip to content
This repository has been archived by the owner on Feb 26, 2020. It is now read-only.

More options for time-based reaping #6

Open
atombender opened this issue Oct 27, 2017 · 0 comments
Open

More options for time-based reaping #6

atombender opened this issue Oct 27, 2017 · 0 comments

Comments

@atombender
Copy link
Contributor

As far as I can see from the code, all dead jobs are deleted. There's also an option to decide what to do with failed jobs.

However, it's a good idea to be able to keep some dead jobs around for historical purposes, regardless of success or failure. In particular, dead job pods can be inspected for data and logs.

For that reason, I'd like an option to keep jobs by age. For example, if we have a backup job that runs every day, I'd like to keep the last 5 days' worth around.

Secondly, keeping failed jobs is okay, but keeping them for ever may not be what we want. A separate age setting for failed jobs would good.

For me, a time-based setting would work. Perhaps specified as command-line flags (--succeeded-job-ttl=<seconds>, --failed-job-ttl=<seconds>) and/or annotations.

@atombender atombender changed the title More options about what pods to keep More options for time-based reaping Oct 27, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant