Home โบ Convert โบ Jenkins to Kubernetes
Convert Jenkins cron to Kubernetes
Jenkins expressions look similar to Kubernetes, but the differences matter. Paste yours below; the result is checked against the original run times.
What changes from Jenkins to Kubernetes
- Jenkins
Hvalues pick a per-job offset, which no other system has. The converter replaces them with the start of the range.
Worked examples
| Schedule | Jenkins | Kubernetes |
|---|---|---|
| every minute | * * * * * | * * * * * |
| every weekday at 8:30 AM | 30 8 * * 1-5 | 30 8 * * 1-5 |
Conversions that come with a warning
- every 5 minutes:
H/5 * * * *โ*/5 * * * *. Jenkins H values have no equivalent elsewhere; they were replaced by their range start. - every 10 minutes:
H/10 * * * *โ*/10 * * * *. Jenkins H values have no equivalent elsewhere; they were replaced by their range start. - every 15 minutes:
H/15 * * * *โ*/15 * * * *. Jenkins H values have no equivalent elsewhere; they were replaced by their range start. - every 30 minutes:
H/30 * * * *โ*/30 * * * *. Jenkins H values have no equivalent elsewhere; they were replaced by their range start.
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).
Jenkins uses the controller's time zone. Put TZ=Asia/Kolkata on its own first line of the trigger to override it.
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.
Go the other way
Convert Kubernetes to Jenkins, or open the Jenkins builder or the Kubernetes builder.
Frequently asked questions
How do I convert a Jenkins cron expression to Kubernetes?
Paste it into the converter above with Jenkins as the source and Kubernetes as the target. For example, * * * * * becomes * * * * *.
Is every Jenkins expression convertible to Kubernetes?
Yes for the common schedules we tested (27 of 27), though unusual expressions with special characters might need manual review.
Does Kubernetes run in the same time zone as Jenkins?
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.