Home โบ Cron โบ Kubernetes
Kubernetes CronJob Schedule Generator
A Kubernetes CronJob uses the standard five-field cron format in spec.schedule. Check when it will fire and copy a complete manifest.
Your week at a glance
Upcoming runs
| # | Local | UTC | From now |
|---|
Copy-ready code
What to know about Kubernetes cron
- Five fields: minute, hour, day-of-month, month, day-of-week.
- Since Kubernetes 1.27, set
spec.timeZone(for exampleAsia/Kolkata). Without it, the schedule uses the time zone of the kube-controller-manager, which is often UTC. - Set
concurrencyPolicy: Forbidif a slow run must not overlap the next one. - If both day-of-month and day-of-week are restricted, the job runs when either matches.
Common Kubernetes schedules
Ready-made expressions for the schedules people search for most. Each page explains the expression and shows the first run times.
Frequently asked questions
What time zone does a Kubernetes CronJob use?
The controller's zone unless you set spec.timeZone (stable from 1.27). Always set it explicitly.
Can I use seconds in a CronJob schedule?
No. The minimum interval is one minute.
Why did my CronJob not run?
Common causes: the job missed its window past startingDeadlineSeconds, the CronJob is suspended, or too many missed runs (over 100) accumulated.
Moving a schedule between systems? Use the cron format converter, or read the cron error fixes.