-
Notifications
You must be signed in to change notification settings - Fork 3
chore: streamline k8s job TTLs #1008
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
outdooracorn
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! 🚀
| ], | ||
| 'spec' => [ | ||
| 'ttlSecondsAfterFinished' => 0, | ||
| 'ttlSecondsAfterFinished' => 24 * 60 * 60 * 7, // 1 week |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Probably does make sense to keep these around for a while
| ], | ||
| 'spec' => [ | ||
| 'ttlSecondsAfterFinished' => 14 * 24 * 60 * 60, // 2 weeks | ||
| 'ttlSecondsAfterFinished' => 24 * 60 * 60 * 7, // 1 week |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see no issue moving from 2 weeks to one week here. There is a small chance that this means we'll have all been away and are unable to inspect something here but that's probably the case with any length of time we pick
Co-authored-by: Thomas Arrow <tarrow@users.noreply.github.com>
I challenge these configs and propose to streamline this to at least 1 week for all current jobs.
Reason: jobs with 0 TTL are almost impossible to inspect
Question: does anyone know the choice for these settings or can see any downsides to a change like this?