From 7da5b129271a78d579c4b14cf5986283124705fb Mon Sep 17 00:00:00 2001 From: Tim Bannister Date: Sun, 23 Feb 2020 10:13:03 +0000 Subject: [PATCH] Note CronJob timezone comes from system timezone The timezone for the kube-controller-manager (or if that's broken apart, the cronjob controller) determines when CronJobs are scheduled. This reverts commit bad124b857a2927b75be739646244aacc5190580. --- 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 0752a14c1a..d44714836d 100644 --- a/content/en/docs/concepts/workloads/controllers/cron-jobs.md +++ b/content/en/docs/concepts/workloads/controllers/cron-jobs.md @@ -18,7 +18,7 @@ One CronJob object is like one line of a _crontab_ (cron table) file. It runs a on a given schedule, written in [Cron](https://en.wikipedia.org/wiki/Cron) format. {{< note >}} -All **CronJob** `schedule:` times are denoted in UTC. +All **CronJob** `schedule:` times are based on the timezone of the master where the job is initiated. {{< /note >}} When creating the manifest for a CronJob resource, make sure the name you provide