advancedScenario & System Design Questions

CronJob job misses scheduled runs for 3 hours

Check whether startingDeadlineSeconds is set -- if it is too short and the cluster was briefly unavailable, missed runs beyond the deadline are permanently skipped. Also check concurrencyPolicy: Forbid with a long-running previous run.

This is a Pro chapter

Sign in, then upgrade to Pro or Power to unlock this and the full DevOps Mastery library.

CronJob job misses scheduled runs for 3 hours

Next Step

Continue to StatefulSet postgres-1 rescheduled to a new node but shows missing data← Back to all Kubernetes questions