Skip to content

Commit 0be2a69

Browse files
authored
Merge pull request #20301 from sftim/20200413_fix_cronjob_timezone_note
Note CronJob timezone comes from system timezone
2 parents 460b65f + 6a97c40 commit 0be2a69

File tree

1 file changed

+8
-3
lines changed

1 file changed

+8
-3
lines changed

content/en/docs/concepts/workloads/controllers/cron-jobs.md

Lines changed: 8 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -17,9 +17,14 @@ A _CronJob_ creates {{< glossary_tooltip term_id="job" text="Jobs" >}} on a repe
1717
One CronJob object is like one line of a _crontab_ (cron table) file. It runs a job periodically
1818
on a given schedule, written in [Cron](https://en.wikipedia.org/wiki/Cron) format.
1919

20-
{{< note >}}
21-
All **CronJob** `schedule:` times are denoted in UTC.
22-
{{< /note >}}
20+
{{< caution >}}
21+
All **CronJob** `schedule:` times are based on the timezone of the
22+
{{< glossary_tooltip term_id="kube-controller-manager" text="kube-controller-manager" >}}.
23+
24+
If your control plane runs the kube-controller-manager in Pods or bare
25+
containers, the timezone set for the kube-controller-manager container determines the timezone
26+
that the cron job controller uses.
27+
{{< /caution >}}
2328

2429
When creating the manifest for a CronJob resource, make sure the name you provide
2530
is a valid [DNS subdomain name](/docs/concepts/overview/working-with-objects/names#dns-subdomain-names).

0 commit comments

Comments
 (0)