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
Hi, I started browsing issues section just to report about this issue with this question. Few further observations about this issue (the asked question is "to terminate the the cron job" if it takes more than 17 seconds to start execution after its schedule):
startingDeadlineSeconds doesn't offer any cronjob termination. It just captures that specific job instantiation as failure. Infact, there is no such property for cron job to terminate the cron job itself.
The question & the provided solution would have been correct if it is worded to terminate the job that is associated with the cronjob if it exceeds more than 17 seconds. Because each cronjob instantiation creates a new job and new pods within that job, hence terminating that new job would had made sense.
Hi there,
First, congratulations on such an amazing compilation of exercises! Good job indeed!
I believe there is a mistake at the Cron jobs's last exercise. The solution should be to add startingDeadlineSeconds instead of activeDeadlineSeconds.
activeDeadlineSeconds is for Jobs as per Job Termination and Cleanup section.
startingDeadlineSeconds is for CronJobs, as per Starting Deadline section
The text was updated successfully, but these errors were encountered: