You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm currently using k3d for local development. I need to run several cron jobs and would like them to be managed by Kubernetes and run in the cluster. Everything is working as expected until I put my laptop to sleep for a certain amount of time (cron schedule period * 100). If any cron hits the 100 missed execution threshold, the cron job will stop attempting to execute with the following message.
Cannot determine if job needs to be started: too many missed start time (> 100). Set or decrease .spec.startingDeadlineSeconds or check clock skew
Deleting and reprovisioning the jobs gets them going again, but this is not ideal. Is there any way around this behavior? I do not see any way to increase missed cron threshold
This discussion was converted from issue #523 on March 03, 2021 15:31.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I'm currently using k3d for local development. I need to run several cron jobs and would like them to be managed by Kubernetes and run in the cluster. Everything is working as expected until I put my laptop to sleep for a certain amount of time (cron schedule period * 100). If any cron hits the 100 missed execution threshold, the cron job will stop attempting to execute with the following message.
Deleting and reprovisioning the jobs gets them going again, but this is not ideal. Is there any way around this behavior? I do not see any way to increase missed cron threshold
Beta Was this translation helpful? Give feedback.
All reactions