#13 add startingDeadlineSeconds

Merged
hjacobs merged 1 commits from droopy4096/kube-janitor:add_startingDeadlineSeconds into main 3 months ago

in cases where cronjob controller goes offline for a prolongued period of time new jobs cannot start since kubernetes assumes that there were over a 100 failures (which is a default threshold) and refuses to start new jobs at all. Setting startingDeadlineSeconds to a reasonable length in seconds allows to overcome that limitation. So, with cron set to run every 5 min we shouln't see more 100 failures within, say 200min (200*60 == 12000). Setting it to a even lower number basically ensures that jobs will always run even if cluster/controler was offline for a longer period of time.

in cases where cronjob controller goes offline for a prolongued period of time new jobs cannot start since kubernetes assumes that there were over a 100 failures (which is a default threshold) and refuses to start new jobs at all. Setting `startingDeadlineSeconds` to a reasonable length in seconds allows to overcome that limitation. So, with cron set to run every 5 min we shouln't see more 100 failures within, say 200min (200\*60 == 12000). Setting it to a even lower number basically ensures that jobs will always run even if cluster/controler was offline for a longer period of time.
droopy4096 added 1 commit 3 months ago
hjacobs merged commit 9f34243f63 into main 3 months ago
The pull request has been merged as 9f34243f63.
Sign in to join this conversation.
No reviewers
No Milestone
No Assignees
1 Participants
Notifications
Due Date

No due date set.

Dependencies

This pull request currently doesn't have any dependencies.

Loading…
There is no content yet.