Home › Convert › Kubernetes to Apache Airflow
Convert Kubernetes cron to Apache Airflow
Kubernetes expressions look similar to Apache Airflow, but the differences matter. Paste yours below; the result is checked against the original run times.
What changes from Kubernetes to Apache Airflow
- Kubernetes and Apache Airflow use the same five-field layout and weekday numbering, so most expressions convert unchanged.
Worked examples
| Schedule | Kubernetes | Apache Airflow |
|---|---|---|
| every minute | * * * * * | * * * * * |
| every 5 minutes | */5 * * * * | */5 * * * * |
| every 10 minutes | */10 * * * * | */10 * * * * |
| every 15 minutes | */15 * * * * | */15 * * * * |
| every 30 minutes | */30 * * * * | */30 * * * * |
| every hour | 0 * * * * | 0 * * * * |
| every 2 hours | 0 */2 * * * | 0 */2 * * * |
| every 3 hours | 0 */3 * * * | 0 */3 * * * |
Field layout and time zones
minute (0-59), hour (0-23), day-of-month (1-31), month (1-12), day-of-week (0-7, 0 and 7 = Sunday).
Set spec.timeZone (Kubernetes 1.27+) to a name like Asia/Kolkata. Without it the schedule follows the controller's time zone, usually UTC.
minute (0-59), hour (0-23), day-of-month (1-31), month (1-12), day-of-week (0-7, 0 and 7 = Sunday).
Airflow defaults to UTC. On a time-zone-aware DAG a cron schedule follows wall-clock time, so a daily 00:00 US/Eastern run moves between 04:00 and 05:00 UTC across daylight saving changes.
Go the other way
Convert Apache Airflow to Kubernetes, or open the Kubernetes builder or the Apache Airflow builder.
Frequently asked questions
How do I convert a Kubernetes cron expression to Apache Airflow?
Paste it into the converter above with Kubernetes as the source and Apache Airflow as the target. For example, * * * * * becomes * * * * *.
Is every Kubernetes expression convertible to Apache Airflow?
Yes for the common schedules we tested (27 of 27), though unusual expressions with special characters might need manual review.
Does Apache Airflow run in the same time zone as Kubernetes?
Not necessarily. Conversion changes the syntax, not the time zone. Check where each system evaluates the schedule before you rely on the same clock times.