From f34e176d268f7c635aa75da718a85f53a8b3d7d9 Mon Sep 17 00:00:00 2001 From: Harold Cheng Date: Wed, 7 Dec 2022 21:30:05 +0800 Subject: [PATCH] update the description of timezone --- .../concepts/workloads/controllers/cron-jobs.md | 17 +---------------- 1 file changed, 1 insertion(+), 16 deletions(-) diff --git a/content/en/docs/concepts/workloads/controllers/cron-jobs.md b/content/en/docs/concepts/workloads/controllers/cron-jobs.md index f1b2df52bc..277e7a302c 100644 --- a/content/en/docs/concepts/workloads/controllers/cron-jobs.md +++ b/content/en/docs/concepts/workloads/controllers/cron-jobs.md @@ -97,22 +97,7 @@ Other than the standard syntax, some macros like `@monthly` can also be used: | @hourly | Run once an hour at the beginning of the hour | 0 * * * * | {{< caution >}} -All **CronJob** `schedule:` times are based on the timezone of the -{{< glossary_tooltip term_id="kube-controller-manager" text="kube-controller-manager" >}}. - -If your control plane runs the kube-controller-manager in Pods or bare -containers, the timezone set for the kube-controller-manager container determines the timezone -that the CronJob controller uses. -{{< /caution >}} - -{{< caution >}} -The [v1 CronJob API](/docs/reference/kubernetes-api/workload-resources/cron-job-v1/) -does not officially support setting timezone as explained above. - -Setting variables such as `CRON_TZ` or `TZ` is not officially supported by the Kubernetes project. -`CRON_TZ` or `TZ` is an implementation detail of the internal library being used -for parsing and calculating the next Job creation time. Any usage of it is not -recommended in a production cluster. +Historically you may find the `.spec.schedule` field can be set with a timezone like `CRON_TZ=UTC * * * * *`. This way is not recommended any more and you should consider use the `.spec.timeZone` field as described below. {{< /caution >}} To generate CronJob schedule expressions, you can also use web tools like [crontab.guru](https://crontab.guru/).