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

Remove or allow customization of CronJob missed start times #83642

Open
vllry opened this issue Oct 8, 2019 · 1 comment

Comments

@vllry
Copy link
Contributor

commented Oct 8, 2019

What would you like to be added:
Remove the "missed start times" suspension on CronJobs, OR allow this behavior to be customized.

Why is this needed:
CronJobs will suspend if 100 start times are missed. There are many ways that this could happen:

  • Pods get stuck in Pending/Init
  • Containers are crashing (bad version, bad data/APIs, etc)
  • A job runs for a very long time

This behavior may be useful in some cases, but it is also extremely frustrating, and makes CronJobs a very hands-on resource. For example, if a service owner deploys a bad change that breaks a minutely cronjob, they have 100 minutes to deploy the fix, or they will need to alter the CronJob object.

@vllry

This comment has been minimized.

Copy link
Contributor Author

commented Oct 8, 2019

/sig apps

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.