K8s CronJob Schedule Builder
Build a Kubernetes CronJob YAML with timezone awareness. Preview the next runs in your local time.
Coming soon. Tool implementation in progress.
About the K8s CronJob Schedule Builder
This tool will help you build correct, timezone-aware CronJob manifests for Kubernetes 1.27+ — including a live preview of the next several runs in your local time. The full implementation is being scaffolded; the page chrome you see here is a placeholder while the interactive UI is wired up.
Frequently asked questions
Does Kubernetes CronJob support timezones?
Yes — since Kubernetes 1.27, CronJob supports a timeZone field that accepts any IANA time zone name. Earlier versions interpret schedules in the kube-controller-manager's local time, which is almost always UTC.
How is a Kubernetes CronJob schedule different from regular cron?
The schedule field uses standard cron syntax (five fields: minute, hour, day-of-month, month, day-of-week). The differences are operational: missed runs are tracked via startingDeadlineSeconds, concurrency is governed by concurrencyPolicy, and the controller runs the job rather than crond on a host.
Why does my CronJob fire at a slightly different time than expected?
The CronJob controller polls every 10 seconds, so triggering can drift by up to that much. Heavy controller load, API server latency, or a misconfigured timeZone field can introduce additional drift.