Home › Convert › Kubernetes to Google Cloud Scheduler
Convert Kubernetes cron to Google Cloud Scheduler
Kubernetes expressions look similar to Google Cloud Scheduler, but the differences matter. Paste yours below; the result is checked against the original run times.
What changes from Kubernetes to Google Cloud Scheduler
- Kubernetes and Google Cloud Scheduler use the same five-field layout and weekday numbering, so most expressions convert unchanged.
Worked examples
| Schedule | Kubernetes | Google Cloud Scheduler |
|---|---|---|
| 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).
Cloud Scheduler takes any tz database zone (default UTC) and runs on wall-clock time, so daylight saving can make jobs run or not run unexpectedly. Google recommends UTC to avoid that.
Go the other way
Convert Google Cloud Scheduler to Kubernetes, or open the Kubernetes builder or the Google Cloud Scheduler builder.
Frequently asked questions
How do I convert a Kubernetes cron expression to Google Cloud Scheduler?
Paste it into the converter above with Kubernetes as the source and Google Cloud Scheduler as the target. For example, * * * * * becomes * * * * *.
Is every Kubernetes expression convertible to Google Cloud Scheduler?
Yes for the common schedules we tested (27 of 27), though unusual expressions with special characters might need manual review.
Does Google Cloud Scheduler 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.