From 2a192c2af508c98f97bc1bca733a35d9018045c2 Mon Sep 17 00:00:00 2001 From: Fabian Baumanis Date: Thu, 20 Feb 2020 21:41:58 +0100 Subject: [PATCH] Change back cronjob timezone note to UTC (#18715) --- .../docs/concepts/workloads/controllers/cron-jobs.md | 11 +++-------- 1 file changed, 3 insertions(+), 8 deletions(-) diff --git a/content/en/docs/concepts/workloads/controllers/cron-jobs.md b/content/en/docs/concepts/workloads/controllers/cron-jobs.md index f1bfca9519..6464b6ed04 100644 --- a/content/en/docs/concepts/workloads/controllers/cron-jobs.md +++ b/content/en/docs/concepts/workloads/controllers/cron-jobs.md @@ -17,14 +17,9 @@ A _Cron Job_ creates [Jobs](/docs/concepts/workloads/controllers/jobs-run-to-com One CronJob object is like one line of a _crontab_ (cron table) file. It runs a job periodically on a given schedule, written in [Cron](https://en.wikipedia.org/wiki/Cron) format. -{{< 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 cron job controller uses. -{{< /caution >}} +{{< note >}} +All **CronJob** `schedule:` times are denoted in UTC. +{{< /note >}} When creating the manifest for a CronJob resource, make sure the name you provide is a valid [DNS subdomain name](/docs/concepts/overview/working-with-objects/names#dns-subdomain-names).