Home โบ Kubernetes โบ Every day at 2:00 AM
Kubernetes cron expression: every day at 2:00 AM
To run a Kubernetes job every day at 2:00 AM, use:
0 2 * * *At 02:00 UTC.
Your week at a glance
Upcoming runs
| # | Local | UTC | From now |
|---|
Copy-ready code
Why use this schedule
A quiet, low-traffic hour, popular for backups and heavy maintenance. Most user-facing systems are at their lightest around this time, so a slow job is less likely to be noticed.
- Full database backups
- Reindexing and vacuum jobs
- Dependency or image rebuilds
First runs, as an example
Starting from 1 January 2027, evaluated in UTC:
| # | Date and time (UTC) |
|---|---|
| 1 | Fri, 01 Jan 2027, 02:00:00 |
| 2 | Sat, 02 Jan 2027, 02:00:00 |
| 3 | Sun, 03 Jan 2027, 02:00:00 |
| 4 | Mon, 04 Jan 2027, 02:00:00 |
| 5 | Tue, 05 Jan 2027, 02:00:00 |
| 6 | Wed, 06 Jan 2027, 02:00:00 |
Every day at 2:00 AM in every dialect
| System | Expression |
|---|---|
| Kubernetes (this page) | 0 2 * * * |
| Quartz | 0 0 2 * * ? |
| Spring | 0 0 2 * * * |
| Crontab | 0 2 * * * |
| AWS EventBridge | 0 2 * * ? * |
| Jenkins | H 2 * * * |
| GitHub Actions | 0 2 * * * |
| node-cron | 0 2 * * * |
| Apache Airflow | 0 2 * * * |
| Azure Functions | 0 0 2 * * * |
| Google Cloud Scheduler | 0 2 * * * |
Need to translate a different expression? Use the cron converter.
Ready-to-use Kubernetes config
Drop this into your project. The expression is the one above.
apiVersion: batch/v1
kind: CronJob
metadata:
name: my-job
spec:
schedule: "0 2 * * *"
timeZone: "Etc/UTC"
concurrencyPolicy: Forbid
jobTemplate:
spec:
template:
spec:
restartPolicy: OnFailure
containers:
- name: job
image: busybox
command: ["sh", "-c", "date"]The Kubernetes fields, in order: minute (0-59), hour (0-23), day-of-month (1-31), month (1-12), day-of-week (0-7, 0 and 7 = Sunday).
Things to watch out for in Kubernetes
- A CronJob creates a new Job object each run. Set concurrencyPolicy and startingDeadlineSeconds so missed runs behave as you expect.
- Set spec.timeZone (Kubernetes 1.27+) to a name like Asia/Kolkata. Without it the schedule follows the controller's time zone, usually UTC.
The common mistake with this schedule
02:00 is a trap in daylight-saving zones: on the spring-forward night that hour does not exist, so the job may be skipped or run late. Run it in UTC or pick another time.
Frequently asked questions
How do I run a Kubernetes job every day at 2:00 AM?
Use 0 2 * * *. At 02:00 UTC.
What is the every day at 2:00 AM cron expression in other systems?
Quartz: 0 0 2 * * ?; Spring: 0 0 2 * * *; Crontab: 0 2 * * *. The table on this page lists every dialect.
Which time zone does Kubernetes use for this schedule?
Set spec.timeZone (Kubernetes 1.27+) to a name like Asia/Kolkata. Without it the schedule follows the controller's time zone, usually UTC.