Kubernetes CronJob DST and Timezone Guide

Kubernetes CronJob uses standard five-field cron in spec.schedule. Since Kubernetes 1.27, spec.timeZone accepts an IANA name so jobs can follow local wall-clock time instead of the control plane UTC default.

UTC vs named timezone

UTC schedules are stable across DST but may not match business hours in a region. A named timezone keeps 09:00 local on weekdays but shifts the UTC instant when offsets change.

Preview before apply

Build the schedule in CronWizard, set the cluster timezone, preview next runs, then export a CronJob manifest. Validate that spec.timeZone matches the business requirement documented in the runbook.

Overlap and concurrency

Use concurrencyPolicy: Forbid or Replace when jobs must not overlap. DST does not remove the need for timeout and retry discipline.