Change:
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. --<!--Required Information--Problem: PR highlights that the documentation for CronJob is out of date since the v1.22 release. We're now using the revised controller by default (with no option to revert) and also a different syntax for the schedule. Proposed Solution: Identify stale or incorrect data on the pages about CronJobs Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--Kubernetes Version: v.122 Additional Information: /kind bug /sig apps Relevant to
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details

Discussion:
<!-- overview --> <del> {{< feature-state for_k8s_version="v1.21" state="stable" >}} </del> <ins> {{< feature-state for_k8s_version="v1.22" state="stable" >}} </ins> A _CronJob_ creates {{< glossary_tooltip term_id="job" text="Jobs" >}} on a repeating schedule. 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. <ins> In addition, the CronJob schedule supports timezone handling, you can specify the timezone by adding "CRON_TZ=<time zone>" at the beginning of the CronJob schedule, and it is recommended to always set `CRON_TZ`. </ins> {{< caution >}} All **CronJob** `schedule:` times are based on the timezone of the {{< glossary_tooltip term_id="kube-controller-manager" text="kube-controller-manager" >}}.

### Cron schedule syntax ``` <del> # ┌───────────── minute (0 - 59) # │ ┌───────────── hour (0 - 23) # │ │ ┌───────────── day of the month (1 - 31) # │ │ │ ┌───────────── month (1 - 12) # │ │ │ │ ┌───────────── day of the week (0 - 6) (Sunday to Saturday; # │ │ │ │ │                                   7 is also Sunday on some systems) # │ │ │ │ │ # │ │ │ │ │ # * * * * * </del> <ins> #      ┌────────────────── timezone (optional) #      |      ┌───────────── minute (0 - 59) #      |      │ ┌───────────── hour (0 - 23) #      |      │ │ ┌───────────── day of the month (1 - 31) #      |      │ │ │ ┌───────────── month (1 - 12) #      |      │ │ │ │ ┌───────────── day of the week (0 - 6) (Sunday to Saturday; #      |      │ │ │ │ │                                   7 is also Sunday on some systems) #      |      │ │ │ │ │ #      |      │ │ │ │ │ # CRON_TZ=UTC * * * * * </ins> ```

<del> For example, the line below states that the task must be started every Friday at midnight, as well as on the 13th of each month at midnight: </del> <ins> For example, the line below states that the task must be started every Friday at midnight, as well as on the 13th of each month at midnight(in UTC): </ins> <del> `0 0 13 * 5` </del> <ins> `CRON_TZ=UTC 0 0 13 * 5` </ins> To generate CronJob schedule expressions, you can also use web tools like [crontab.guru](https://crontab.guru/).