Skip to content

Conversation

@deer-wmde
Copy link
Contributor

@deer-wmde deer-wmde commented Nov 21, 2025

  • I noticed we set different TTL (time to live) for the k8s we schedule
  • The job specs in the deploy repo specify mostly 1 week (example)
  • Here in the API we have currently
    • one with two weeks
    • two jobs with 0 seconds

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?

Copy link
Member

@outdooracorn outdooracorn left a 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
Copy link
Contributor

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
Copy link
Contributor

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>
@outdooracorn outdooracorn merged commit 1fa0de6 into main Dec 8, 2025
5 checks passed
@outdooracorn outdooracorn deleted the de/streamline-job-ttl branch December 8, 2025 17:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants