Home โบ Kubernetes โบ Every 6 hours
Kubernetes cron expression: every 6 hours
To run a Kubernetes job every 6 hours, use:
0 */6 * * *At minute 0, every 6 hours.
Your week at a glance
Upcoming runs
| # | Local | UTC | From now |
|---|
Copy-ready code
Why use this schedule
Four runs a day at 00:00, 06:00, 12:00 and 18:00. A popular backup and report rhythm.
- Incremental backups
- Re-crawling sitemaps
- Recomputing leaderboards
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 | Fri, 01 Jan 2027, 06:00:00 |
| 3 | Fri, 01 Jan 2027, 12:00:00 |
| 4 | Fri, 01 Jan 2027, 18:00:00 |
| 5 | Sat, 02 Jan 2027, 00:00:00 |
| 6 | Sat, 02 Jan 2027, 06:00:00 |
Every 6 hours in every dialect
| System | Expression |
|---|---|
| Kubernetes (this page) | 0 */6 * * * |
| Quartz | 0 0 */6 * * ? |
| Spring | 0 0 */6 * * * |
| Crontab | 0 */6 * * * |
| AWS EventBridge | 0 */6 * * ? * |
| Jenkins | H */6 * * * |
| GitHub Actions | 0 */6 * * * |
| node-cron | 0 */6 * * * |
| Apache Airflow | 0 */6 * * * |
| Azure Functions | 0 0 */6 * * * |
| Google Cloud Scheduler | 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 */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
- Kubernetes CronJobs run at most once per minute, and the controller checks about every ten seconds, so exact timing can drift by seconds.
- 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 hours are fixed on the clock, not relative to when you deployed. Deploying at 07:00 does not make the next run 13:00.
Frequently asked questions
How do I run a Kubernetes job every 6 hours?
Use 0 */6 * * *. At minute 0, every 6 hours.
What is the every 6 hours cron expression in other systems?
Quartz: 0 0 */6 * * ?; Spring: 0 0 */6 * * *; Crontab: 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.