Change:
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. <del> {{< note >}} All **CronJob** `schedule:` times are denoted in UTC. {{< /note >}} </del> <ins> {{< 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 >}} </ins> 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).

Discussion:
This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --We have setup the Kuberntes cluster in our Environment we have 2 master node and 4 worker node which all installed EST Time zone Cron Job is scheduled at 12:01 daily midnight And Job is started on 19:01 EST Time instead of 12:01 Time , I feel this running as UTC Timezone <!--Required Information--Problem: The cron Job is not running on the timezone of the master node its running on the UTC Timezone ie OS layer of your Docker image Proposed Solution: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--v1.13.1 <!--Additional Information:--
It looks like this is a duplicate of issue

It seems that this note is inaccurate by saying it's based on timezone. In fact messaging is alluding that timezone will not be supported and it's based on UTC.
Here's the change for posterity.
Thanks for reporting this /kind bug /priority important-longterm /good-first-issue
/assign
Hello Team Is there any deadline when this issue will be fixed ? can we get the the Timezone functionality also with thes CronJob Just want to know
Kubernetes is an open-source, volunteer led project. There aren't deadlines per se. If you're keen to see the documentation changed, for this or any issue, anyone can .
(If anyone would like to help here but is not sure how to get started, please reply&mdash;advice is available).
The change is wrong, the time IS taken from the master node the controller is running on, or from within the container controller-manager is running. It's not hardcoded to be UTC. Why are you claiming otherwise, have you checked?
Ah, so this issue is invalid and needs reverting?
(alternative fix: revert, then revise so that all times are_ in UTC)
I looked at the code: and it looks to me that this issue is invalid. I propose to close it if there's no update in the next fortnight. /remove-good-first-issue /remove-help /remove-kind bug /remove-priority important-longterm
Is this issue not valid ? , In our instance , we have 2 master node and it configured as EST timezone and 4 worker node and configured as EST timezone , but still cron job runs on the UTC Timezone
Is the advice at https://deploy-preview---kubernetes-io-master- accurate?
Okay thanks!! Now document looks aligned thanks we can close!!