Home โบ Kubernetes โบ Every 10 minutes
Kubernetes cron expression: every 10 minutes
To run a Kubernetes job every 10 minutes, use:
*/10 * * * *Every 10 minutes.
Your week at a glance
Upcoming runs
| # | Local | UTC | From now |
|---|
Copy-ready code
Why use this schedule
Six runs an hour. Good for work that is worth doing often but not constantly, such as pulling metrics or checking for stale records.
- Collecting metrics into a time-series store
- Retrying failed webhook deliveries
- Rebuilding a search index delta
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, 00:10:00 |
| 3 | Fri, 01 Jan 2027, 00:20:00 |
| 4 | Fri, 01 Jan 2027, 00:30:00 |
| 5 | Fri, 01 Jan 2027, 00:40:00 |
| 6 | Fri, 01 Jan 2027, 00:50:00 |
Every 10 minutes in every dialect
| System | Expression |
|---|---|
| Kubernetes (this page) | */10 * * * * |
| Quartz | 0 */10 * * * ? |
| Spring | 0 */10 * * * * |
| Crontab | */10 * * * * |
| AWS EventBridge | */10 * * * ? * |
| Jenkins | H/10 * * * * |
| GitHub Actions | */10 * * * * |
| node-cron | */10 * * * * |
| Apache Airflow | */10 * * * * |
| Azure Functions | 0 */10 * * * * |
| Google Cloud Scheduler | */10 * * * * |
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: "*/10 * * * *"
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.
- 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
Because 10 divides 60 evenly the gaps are always exactly ten minutes. That is not true for steps like 7 or 25, which restart at the top of every hour.
Frequently asked questions
How do I run a Kubernetes job every 10 minutes?
Use */10 * * * *. Every 10 minutes.
What is the every 10 minutes cron expression in other systems?
Quartz: 0 */10 * * * ?; Spring: 0 */10 * * * *; Crontab: */10 * * * *. 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.