Home โบ Kubernetes โบ Every Saturday and Sunday at 10:00 AM
Kubernetes cron expression: every Saturday and Sunday at 10:00 AM
To run a Kubernetes job every Saturday and Sunday at 10:00 AM, use:
0 10 * * 0,6At 10:00 UTC, on Sun and Sat.
Your week at a glance
Upcoming runs
| # | Local | UTC | From now |
|---|
Copy-ready code
Why use this schedule
Weekend-only work: batch jobs that should not compete with weekday traffic.
- Weekend full reindexing
- Weekly cleanup of staging data
- Weekend report digests
First runs, as an example
Starting from 1 January 2027, evaluated in UTC:
| # | Date and time (UTC) |
|---|---|
| 1 | Sat, 02 Jan 2027, 10:00:00 |
| 2 | Sun, 03 Jan 2027, 10:00:00 |
| 3 | Sat, 09 Jan 2027, 10:00:00 |
| 4 | Sun, 10 Jan 2027, 10:00:00 |
| 5 | Sat, 16 Jan 2027, 10:00:00 |
| 6 | Sun, 17 Jan 2027, 10:00:00 |
Every Saturday and Sunday at 10:00 AM in every dialect
| System | Expression |
|---|---|
| Kubernetes (this page) | 0 10 * * 0,6 |
| Quartz | 0 0 10 ? * 1,7 |
| Spring | 0 0 10 * * 0,6 |
| Crontab | 0 10 * * 0,6 |
| AWS EventBridge | 0 10 ? * 1,7 * |
| Jenkins | H 10 * * 0,6 |
| GitHub Actions | 0 10 * * 0,6 |
| node-cron | 0 10 * * 0,6 |
| Apache Airflow | 0 10 * * 0,6 |
| Azure Functions | 0 0 10 * * 0,6 |
| Google Cloud Scheduler | 0 10 * * 0,6 |
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 10 * * 0,6"
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
Sunday is 0 (or 7) in Unix, and 1 in Quartz and EventBridge. Saturday is 6 in Unix but 7 in Quartz.
Frequently asked questions
How do I run a Kubernetes job every Saturday and Sunday at 10:00 AM?
Use 0 10 * * 0,6. At 10:00 UTC, on Sun and Sat.
What is the every Saturday and Sunday at 10:00 AM cron expression in other systems?
Quartz: 0 0 10 ? * 1,7; Spring: 0 0 10 * * 0,6; Crontab: 0 10 * * 0,6. 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.