hard20 pts · first answer countskubernetesjobs

CronJob stops after controller downtime

A CronJob runs every minute. After the controller manager was down for about two hours, the CronJob no longer starts and logs "too many missed start times". What setting avoids this?

A.Set concurrencyPolicy: Allow so missed runs start togetherB.Set suspend: true during upgrades and false afterC.Increase failedJobsHistoryLimit above 100D.Set startingDeadlineSeconds so only recent missed runs are counted

Discussion 0

Join free to post in the discussion.

CronJob stops after controller downtime

Discussion 0

Related questions