Home โบ Kubernetes โบ On the first Monday of every month at 9:00 AM
Kubernetes cron expression: on the first Monday of every month at 9:00 AM
To run a Kubernetes job on the first Monday of every month at 9:00 AM, use:
0 9 * * 1At 09:00 UTC, on Mon.
0 9 * * 1 [ "$(date +\%d)" -le 7 ] && /path/to/jobYour week at a glance
Upcoming runs
| # | Local | UTC | From now |
|---|
Copy-ready code
Why use this schedule
A monthly meeting or review that always lands on the first Monday. Calendars make this easy, but cron has no plain "first Monday" rule, so how you express it depends on the system.
- Monthly planning reports
- First-Monday-of-the-month reminders
- Monthly access reviews
First runs, as an example
Starting from 1 January 2027, evaluated in UTC:
| # | Date and time (UTC) |
|---|---|
| 1 | Mon, 04 Jan 2027, 09:00:00 |
| 2 | Mon, 11 Jan 2027, 09:00:00 |
| 3 | Mon, 18 Jan 2027, 09:00:00 |
| 4 | Mon, 25 Jan 2027, 09:00:00 |
| 5 | Mon, 01 Feb 2027, 09:00:00 |
| 6 | Mon, 08 Feb 2027, 09:00:00 |
On the first Monday of every month at 9:00 AM in every dialect
| System | Expression |
|---|---|
| Kubernetes (this page) | 0 9 * * 1 |
| Quartz | 0 0 9 ? * 2#1 |
| Spring | 0 0 9 * * MON#1 |
| Crontab | 0 9 * * 1 |
| AWS EventBridge | 0 9 ? * 2#1 * |
| Jenkins | H 9 * * 1 |
| GitHub Actions | 0 9 * * 1 |
| node-cron | 0 9 1-7 * 1 |
| Apache Airflow | 0 9 * * MON#1 |
| Azure Functions | 0 0 9 * * 1 |
| Google Cloud Scheduler | 0 9 * * 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 9 * * 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
- Day-of-week is 0-6 (or 7) with Sunday as 0, as in standard cron.
- Kubernetes has no L, W or # support. Run the job on a broader schedule and check the date inside the container.
- 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
Writing 0 9 1-7 * 1 in classic cron does not mean "first Monday". Cron ORs the two day fields, so it fires on days 1-7 and every Monday. Use a guard in the script instead.
Frequently asked questions
How do I run a Kubernetes job on the first Monday of every month at 9:00 AM?
Use 0 9 * * 1. At 09:00 UTC, on Mon. This dialect has no native rule for it, so the job must also check the date (see the guard command above).
What is the on the first Monday of every month at 9:00 AM cron expression in other systems?
Quartz: 0 0 9 ? * 2#1; Spring: 0 0 9 * * MON#1; Crontab: 0 9 * * 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.