Change:
<!-- Please only use this template for submitting enhancement requests --What would you like to be : Add CronJob full syntax at and also in the Ex, the line below states that the job must be scheduled every friday as well as the 13th of each month at midnight : 0 0 13 5 Entry Equivalent to -- -- (or 0 0 1 1 0 0 1 0 0 0 (or 0 0 0 N/A Required Remarks -- -- Minutes Hours Day of month ? L W only in some implementations Month Day of week ? L # only in some implementations Year This field is not supported in standard/default implementations Comma ( , ) Commas are used to separate items of a list. For example, using "MON,WED,FRI" in the 5th field (day of week) means Mondays, Wednesdays and Fridays. Dash( - ) Dash defines ranges. For example, 2000-2010 indicates every year between 2000 and 2010, inclusive. Percent ( % ) Percent-signs (%) in the command, unless escaped with backslash (), are changed into newline characters, and all data after the first % are sent to the command as standard input.[13] Non-standard characters The following are non-standard characters and exist only in some cron implementations, such as the Quartz Java scheduler. L 'L' stands for "last". When used in the day-of-week field, it allows specifying constructs such as "the last Friday" ("5L") of a given month. In the day-of-month field, it specifies the last day of the month. Slash (/) In vixie-cron, slashes can be combined with ranges to specify step values.[3] For example, /5 in the minutes field indicates every 5 minutes Hash (#) '#' is allowed for the day-of-week field, and must be followed by a number between one and five. It allows specifying constructs such as "the second Friday" of a given month.[14] For example, entering "5" in the day-of-week field corresponds to the third Friday of every month. Why is this needed: it would be unfair for anyone clearing the CKAD & CKA exams, to fails some questions just because people do not remeber the syntax. /sig docs
/sig docs
Issues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale
Stale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten
Thanks! This is really informative and definitely help to beginners. I would like to add some general examples and use the same format as Can I work on this?
thanks for your reply, yes please feel free to work on it !
/assign shekhar-rajak
/remove-lifecycle rotten
Does k8s actually support those extended features (# offset etc)? Can't find it in the docs anywhere.
Looks like K8s uses for CronJobs And it doesn't support the extended cron syntax.
/transfer website BTW, there is no (permitted) cheatsheet for the Kubernetes certifications. The term “cheat sheet” means a handy lookup and not a guide to answering a specific exam.
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:
([Running Automated Tasks with a CronJob](/docs/tasks/job/automated-tasks-with-cron-jobs/) takes you through this example in more detail). <ins> ### Cron schedule syntax ``` # ┌───────────── 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) # │ │ │ │ │ # │ │ │ │ │ # * * * * * ``` | Entry 										| Description																									| Equivalent to | | ------------- 						| ------------- 																							|-------------  | | @yearly (or @annually)		| Run once a year at midnight of 1 January										| 0 0 1 1 * 		| | @monthly 									| Run once a month at midnight of the first day of the month	| 0 0 1 * * 		| | @weekly 									| Run once a week at midnight on Sunday morning								| 0 0 * * 0 		| | @daily (or @midnight)			| Run once a day at midnight																	| 0 0 * * * 		| | @hourly 									| Run once an hour at the beginning of the hour								| 0 * * * * 		| 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: `0 0 13 * 5` To generate CronJob schedule expressions, you can also use web tools like [crontab.guru](https://crontab.guru/). </ins> ## CronJob limitations {#cron-job-limitations} A cron job creates a job object _about_ once per execution time of its schedule. We say "about" because there