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] 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 >}}