From 845a8855318d3b483fec8c87041cd5fec300d154 Mon Sep 17 00:00:00 2001 From: "salva.gglez" Date: Sun, 6 Dec 2020 17:02:01 +0000 Subject: [PATCH 1/4] Add a caution message on CronJob Controller workload if using startingDeadlineSeconds with a value less than 10s --- content/en/docs/concepts/workloads/controllers/cron-jobs.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/content/en/docs/concepts/workloads/controllers/cron-jobs.md b/content/en/docs/concepts/workloads/controllers/cron-jobs.md index af12bcba25..cdc736aaa5 100644 --- a/content/en/docs/concepts/workloads/controllers/cron-jobs.md +++ b/content/en/docs/concepts/workloads/controllers/cron-jobs.md @@ -61,6 +61,11 @@ If `startingDeadlineSeconds` is set to a large value or left unset (the default) and if `concurrencyPolicy` is set to `Allow`, the jobs will always run at least once. +{{< caution >}} +If `startingDeadlineSeconds` is set to a value less than 10 seconds, then the CronJob may not be scheduled. This is because Cronjob Controller checks things every 10 seconds by default. +{{< /caution >}} + + For every CronJob, the CronJob {{< glossary_tooltip term_id="controller" >}} checks how many schedules it missed in the duration from its last scheduled time until now. If there are more than 100 missed schedules, then it does not start the job and logs the error ```` From d38c74124a89f1978e5d5f74989f439ca0cc8196 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Salvador=20Gonz=C3=A1lez=20Gonz=C3=A1lez?= Date: Sun, 6 Dec 2020 20:08:30 +0000 Subject: [PATCH 2/4] Update content/en/docs/concepts/workloads/controllers/cron-jobs.md Co-authored-by: bl-ue <54780737+bl-ue@users.noreply.github.com> --- content/en/docs/concepts/workloads/controllers/cron-jobs.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/content/en/docs/concepts/workloads/controllers/cron-jobs.md b/content/en/docs/concepts/workloads/controllers/cron-jobs.md index cdc736aaa5..11e30b203d 100644 --- a/content/en/docs/concepts/workloads/controllers/cron-jobs.md +++ b/content/en/docs/concepts/workloads/controllers/cron-jobs.md @@ -62,7 +62,7 @@ and if `concurrencyPolicy` is set to `Allow`, the jobs will always run at least once. {{< caution >}} -If `startingDeadlineSeconds` is set to a value less than 10 seconds, then the CronJob may not be scheduled. This is because Cronjob Controller checks things every 10 seconds by default. +If `startingDeadlineSeconds` is set to a value less than 10 seconds, the CronJob may not be scheduled. This is because the CronJob controller checks things every 10 seconds. {{< /caution >}} @@ -96,4 +96,3 @@ documents the format of CronJob `schedule` fields. For instructions on creating and working with cron jobs, and for an example of CronJob manifest, see [Running automated tasks with cron jobs](/docs/tasks/job/automated-tasks-with-cron-jobs). - From 18b8846b9be9a1f78f432b1867ddf4792143ce44 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Salvador=20Gonz=C3=A1lez=20Gonz=C3=A1lez?= Date: Tue, 8 Dec 2020 11:00:18 +0000 Subject: [PATCH 3/4] Update cron-jobs.md Mention about v2 CronJob controller. --- content/en/docs/concepts/workloads/controllers/cron-jobs.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/concepts/workloads/controllers/cron-jobs.md b/content/en/docs/concepts/workloads/controllers/cron-jobs.md index 11e30b203d..a7e1f03097 100644 --- a/content/en/docs/concepts/workloads/controllers/cron-jobs.md +++ b/content/en/docs/concepts/workloads/controllers/cron-jobs.md @@ -62,7 +62,7 @@ and if `concurrencyPolicy` is set to `Allow`, the jobs will always run at least once. {{< caution >}} -If `startingDeadlineSeconds` is set to a value less than 10 seconds, the CronJob may not be scheduled. This is because the CronJob controller checks things every 10 seconds. +If `startingDeadlineSeconds` is set to a value less than 10 seconds, the CronJob may not be scheduled. This is because the CronJob controller checks things every 10 seconds. As an alpha feature, there is a V2 controller implementation with different behavior. The version 2 controller provides experimental performance improvements. {{< /caution >}} From 9cc4fde6678f8684e0467758e1a520e8ed2ca0ba Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Salvador=20Gonz=C3=A1lez=20Gonz=C3=A1lez?= Date: Sun, 17 Jan 2021 09:36:18 +0000 Subject: [PATCH 4/4] Remove v2 controller mention I removed mention to v2 controller behaviour. --- content/en/docs/concepts/workloads/controllers/cron-jobs.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/concepts/workloads/controllers/cron-jobs.md b/content/en/docs/concepts/workloads/controllers/cron-jobs.md index a7e1f03097..11e30b203d 100644 --- a/content/en/docs/concepts/workloads/controllers/cron-jobs.md +++ b/content/en/docs/concepts/workloads/controllers/cron-jobs.md @@ -62,7 +62,7 @@ and if `concurrencyPolicy` is set to `Allow`, the jobs will always run at least once. {{< caution >}} -If `startingDeadlineSeconds` is set to a value less than 10 seconds, the CronJob may not be scheduled. This is because the CronJob controller checks things every 10 seconds. As an alpha feature, there is a V2 controller implementation with different behavior. The version 2 controller provides experimental performance improvements. +If `startingDeadlineSeconds` is set to a value less than 10 seconds, the CronJob may not be scheduled. This is because the CronJob controller checks things every 10 seconds. {{< /caution >}}