Why Kubernetes CronJob Timezone Handling Breaks Schedules
from DevOps Daily with Fexingo: CI/CD, Kubernetes, and Modern Software Operations Hosted by Fexingo
In this episode of DevOps Daily with Fexingo, Lucas and Luna dive into a surprisingly common failure mode in Kubernetes: CronJob timezone handling. Since Kubernetes 1.22, the CronJob controller treats schedule strings as UTC by default, but many operators assume it honors the node or container timezone. This leads to jobs running hours early or late, especially during daylight saving transitions. Lucas walks through a real incident where a UK-based team's daily cleanup job ran at 9 PM instead of 2 AM every March and October, causing overnight resource spikes. They discuss the `timeZone` field added in 1.24, how to verify it in older clusters, and why even helm charts often miss this. Luna shares a horror story of a production database backup job that silently missed windows for months. The episode closes with a practical checklist: always set `timeZone`, test across DST boundaries, and monitor actual run times vs expected. #Kubernetes #CronJob #Timezone #DevOps #CI/CD #CloudNative #SRE #KubernetesCronJob #TimeZoneBug #DaylightSaving #HelmCharts #Kubernetes124 #ProductionIncident #DatabaseBackup #JobScheduling #TechPodcast #FexingoBusiness #BusinessPodcast Keep every episode free: buymeacoffee.com/fexingo
Embed this episode
No transcript yet.