From d48125d699c1057b23bea3adbfaf7b0f03aad9cf Mon Sep 17 00:00:00 2001 From: unkin-agent Date: Sat, 26 Sep 2026 20:55:32 +1000 Subject: [PATCH] Add job and start deadlines to the g10k-code CronJob (#490) A g10k-code job wedged in ContainerCreating on a failed CephFS mount and never reached a terminal condition, so it stayed in the CronJob active list and `concurrencyPolicy: Forbid` skipped every following minute. No Puppet code reached the estate for 6 days, and the piled-up missed slots crossed the controller 100-slot cap into `TooManyMissedTimes`. The CronJob carried no deadlines at all. - Cap a job at `activeDeadlineSeconds: 300` on the Job spec, so a hang is failed as `DeadlineExceeded` and drops out of the active list (healthy runs take 16-18s). - Set `startingDeadlineSeconds: 200`, bounding missed-schedule look-back to ~3 slots so the count cannot reach 100. Reviewed-on: https://git.unkin.net/unkin/argocd-apps/pulls/490 Co-authored-by: unkin-agent Co-committed-by: unkin-agent --- apps/base/puppet/cronjob_g10k-code.yaml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/apps/base/puppet/cronjob_g10k-code.yaml b/apps/base/puppet/cronjob_g10k-code.yaml index 2b1343c..180f6b7 100644 --- a/apps/base/puppet/cronjob_g10k-code.yaml +++ b/apps/base/puppet/cronjob_g10k-code.yaml @@ -11,11 +11,13 @@ metadata: namespace: puppet spec: schedule: "*/1 * * * *" + startingDeadlineSeconds: 200 concurrencyPolicy: Forbid successfulJobsHistoryLimit: 3 failedJobsHistoryLimit: 3 jobTemplate: spec: + activeDeadlineSeconds: 300 template: metadata: labels: