Home › Convert › Kubernetes to node-cron
Convert Kubernetes cron to node-cron
Kubernetes expressions look similar to node-cron, but the differences matter. Paste yours below; the result is checked against the original run times.
What changes from Kubernetes to node-cron
- node-cron has a leading seconds field. The converter adds
0in front so the job fires at the start of the minute. - Kubernetes runs when day-of-month or day-of-week matches, but node-cron requires both. If you set both fields, the converter warns you.
Worked examples
| Schedule | Kubernetes | node-cron |
|---|---|---|
| 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.
second (0-59), minute (0-59), hour (0-23), day-of-month (1-31), month (1-12), day-of-week (0-7, 0 and 7 = Sunday).
node-cron uses the server time zone unless you pass { timezone: "Asia/Kolkata" }. Its documentation advises timezone: "UTC" for jobs that must not skip or repeat when clocks change.
Go the other way
Convert node-cron to Kubernetes, or open the Kubernetes builder or the node-cron builder.
Frequently asked questions
How do I convert a Kubernetes cron expression to node-cron?
Paste it into the converter above with Kubernetes as the source and node-cron as the target. For example, * * * * * becomes * * * * *.
Is every Kubernetes expression convertible to node-cron?
Yes for the common schedules we tested (27 of 27), though unusual expressions with special characters might need manual review.
Does node-cron 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.