Home โบ Kubernetes โบ Once a year on January 1st
Kubernetes cron expression: once a year on January 1st
To run a Kubernetes job once a year on January 1st, use:
0 0 1 1 *At 00:00 UTC, on the 1st of the month, in Jan.
Your week at a glance
Upcoming runs
| # | Local | UTC | From now |
|---|
Copy-ready code
Why use this schedule
Annual rollovers: new-year counters, yearly archives and licence renewals.
- Resetting annual leave balances
- Yearly archive jobs
- Annual compliance reminders
First runs, as an example
Starting from 1 January 2027, evaluated in UTC:
| # | Date and time (UTC) |
|---|---|
| 1 | Fri, 01 Jan 2027, 00:00:00 |
| 2 | Sat, 01 Jan 2028, 00:00:00 |
| 3 | Mon, 01 Jan 2029, 00:00:00 |
| 4 | Tue, 01 Jan 2030, 00:00:00 |
| 5 | Wed, 01 Jan 2031, 00:00:00 |
| 6 | Thu, 01 Jan 2032, 00:00:00 |
Once a year on January 1st in every dialect
| System | Expression |
|---|---|
| Kubernetes (this page) | 0 0 1 1 * |
| Quartz | 0 0 0 1 1 ? |
| Spring | 0 0 0 1 1 * |
| Crontab | 0 0 1 1 * |
| AWS EventBridge | 0 0 1 1 ? * |
| Jenkins | H 0 1 1 * |
| GitHub Actions | 0 0 1 1 * |
| node-cron | 0 0 1 1 * |
| Apache Airflow | 0 0 1 1 * |
| Azure Functions | 0 0 0 1 1 * |
| Google Cloud Scheduler | 0 0 1 1 * |
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 0 1 1 *"
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
- If both day fields are set, the job runs when either matches. This is standard cron behaviour.
- 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
In Quartz you can add a year field. Without it the schedule repeats every year, which is usually what you want.
Frequently asked questions
How do I run a Kubernetes job once a year on January 1st?
Use 0 0 1 1 *. At 00:00 UTC, on the 1st of the month, in Jan.
What is the once a year on January 1st cron expression in other systems?
Quartz: 0 0 0 1 1 ?; Spring: 0 0 0 1 1 *; Crontab: 0 0 1 1 *. 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.