Skip to content
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

Add startingDeadlineSeconds to cronjob #15

Merged
merged 1 commit into from Sep 10, 2021
Merged

Conversation

eni23
Copy link
Contributor

@eni23 eni23 commented Aug 11, 2021

For every CronJob, the CronJob Controller checks how many schedules it missed in the duration from its last scheduled time until now. If there are more than 100 missed schedules, then it does not start the job and logs the error. If the value is set, the cronjob will survive a cluster downtime.

See: https://access.redhat.com/solutions/3667021 and kubernetes/kubernetes#42649 for details

For every CronJob, the CronJob Controller checks how many schedules it missed in the duration from its last scheduled time until now. If there are more than 100 missed schedules, then it does not start the job and logs the error. If the value is set, the cronjob will survive a cluster downtime.

See: https://access.redhat.com/solutions/3667021 and kubernetes/kubernetes#42649 for details
@eni23 eni23 merged commit 3091ad3 into main Sep 10, 2021
@eni23 eni23 deleted the fix/cronjob-add-deadline-secs branch September 10, 2021 09:35
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.

None yet

2 participants