Home โบ Kubernetes โบ Hourly during business hours on weekdays
Kubernetes cron expression: hourly during business hours on weekdays
To run a Kubernetes job hourly during business hours on weekdays, use:
0 9-17 * * 1-5At minute 0, during hours 09, 10, 11, 12, 13, 14, 15, 16, 17, on Mon, Tue, Wed, Thu and Fri.
Your week at a glance
Upcoming runs
| # | Local | UTC | From now |
|---|
Copy-ready code
Why use this schedule
Hourly, but only from 9 to 17 on weekdays, so nothing runs overnight or at weekends.
- Hourly stock or price snapshots
- Support SLA checks
- Syncing with a partner that only works in office hours
First runs, as an example
Starting from 1 January 2027, evaluated in UTC:
| # | Date and time (UTC) |
|---|---|
| 1 | Fri, 01 Jan 2027, 09:00:00 |
| 2 | Fri, 01 Jan 2027, 10:00:00 |
| 3 | Fri, 01 Jan 2027, 11:00:00 |
| 4 | Fri, 01 Jan 2027, 12:00:00 |
| 5 | Fri, 01 Jan 2027, 13:00:00 |
| 6 | Fri, 01 Jan 2027, 14:00:00 |
Hourly during business hours on weekdays in every dialect
| System | Expression |
|---|---|
| Kubernetes (this page) | 0 9-17 * * 1-5 |
| Quartz | 0 0 9-17 ? * 2-6 |
| Spring | 0 0 9-17 * * 1-5 |
| Crontab | 0 9-17 * * 1-5 |
| AWS EventBridge | 0 9-17 ? * 2-6 * |
| Jenkins | H 9-17 * * 1-5 |
| GitHub Actions | 0 9-17 * * 1-5 |
| node-cron | 0 9-17 * * 1-5 |
| Apache Airflow | 0 9-17 * * 1-5 |
| Azure Functions | 0 0 9-17 * * 1-5 |
| Google Cloud Scheduler | 0 9-17 * * 1-5 |
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-17 * * 1-5"
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.
- 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
9-17 includes hour 17, so the last run is at 17:00, not 16:00. The range is inclusive.
Frequently asked questions
How do I run a Kubernetes job hourly during business hours on weekdays?
Use 0 9-17 * * 1-5. At minute 0, during hours 09, 10, 11, 12, 13, 14, 15, 16, 17, on Mon, Tue, Wed, Thu and Fri.
What is the hourly during business hours on weekdays cron expression in other systems?
Quartz: 0 0 9-17 ? * 2-6; Spring: 0 0 9-17 * * 1-5; Crontab: 0 9-17 * * 1-5. 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.