Kubernetes CronJob Schedule Tester
Check spec.schedule and spec.timeZone before you kubectl apply — next runs, daylight-saving warnings and a copyable CronJob manifest.
Help shape Kubernetes CronJob Schedule Tester
The bug you just noticed will fade in 3 minutes. The feature idea will vanish after your next tab switch. Crazy peps don't suffer silently.
Frequently Asked Questions
Set spec.timeZone to an IANA name like "Europe/Berlin" (stable since Kubernetes 1.27). CRON_TZ or TZ inside the schedule string is rejected — the tester warns you.
Standard 5-field cron plus macros such as @hourly, @daily, @weekly, @monthly and @yearly. “?” is accepted as “*”.
By default they aren't caught up. Set spec.startingDeadlineSeconds to let a late start happen — the generated manifest includes it.
Yes. Paste the YAML into the crontab analyzer: every CronJob's schedule, name and timeZone is extracted and checked.