Home โบ Kubernetes โบ Every weekday at 8:30 AM
Kubernetes cron expression: every weekday at 8:30 AM
To run a Kubernetes job every weekday at 8:30 AM, use:
30 8 * * 1-5At 08:30 UTC, 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
A half-hour offset before the working day starts, so output is waiting by 9.
- Pre-market data loads
- Pre-opening health checks
- Morning briefing emails
First runs, as an example
Starting from 1 January 2027, evaluated in UTC:
| # | Date and time (UTC) |
|---|---|
| 1 | Fri, 01 Jan 2027, 08:30:00 |
| 2 | Mon, 04 Jan 2027, 08:30:00 |
| 3 | Tue, 05 Jan 2027, 08:30:00 |
| 4 | Wed, 06 Jan 2027, 08:30:00 |
| 5 | Thu, 07 Jan 2027, 08:30:00 |
| 6 | Fri, 08 Jan 2027, 08:30:00 |
Every weekday at 8:30 AM in every dialect
| System | Expression |
|---|---|
| Kubernetes (this page) | 30 8 * * 1-5 |
| Quartz | 0 30 8 ? * 2-6 |
| Spring | 0 30 8 * * 1-5 |
| Crontab | 30 8 * * 1-5 |
| AWS EventBridge | 30 8 ? * 2-6 * |
| Jenkins | 30 8 * * 1-5 |
| GitHub Actions | 30 8 * * 1-5 |
| node-cron | 30 8 * * 1-5 |
| Apache Airflow | 30 8 * * 1-5 |
| Azure Functions | 0 30 8 * * 1-5 |
| Google Cloud Scheduler | 30 8 * * 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: "30 8 * * 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
The minute comes first, then the hour. 30 8 means 08:30, while 8 30 would be an invalid hour.
Frequently asked questions
How do I run a Kubernetes job every weekday at 8:30 AM?
Use 30 8 * * 1-5. At 08:30 UTC, on Mon, Tue, Wed, Thu and Fri.
What is the every weekday at 8:30 AM cron expression in other systems?
Quartz: 0 30 8 ? * 2-6; Spring: 0 30 8 * * 1-5; Crontab: 30 8 * * 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.