Why Kubernetes CronJob Timezones Break Production Schedules

Episode notes

In this episode, Lucas and Luna dive into a deceptively tricky Kubernetes feature: CronJob timezone handling. They break down how CronJobs default to UTC regardless of the cluster's regional settings, leading to off-schedule jobs, missed backups, and batch processing failures. Using a real-world example from a fintech company that lost two hours of payment reconciliation data, they explain why the .spec.schedule timezone field added in Kubernetes 1.27 is still underused, and why operators relying on TZ environment variables are playing with fire. They also cover how kube-controller-manager's timezone drift can compound the problem, and share a simple audit command to check all CronJobs for implicit UTC assumptions. If you manage scheduled jobs in Kubernetes, this episode will save you from a midnight pager. #Kubernetes #CronJob #Timezone #DevOps #CloudNative #Scheduling #ProductionBug #Fintech #BatchProcessing #KubeControllerManager #UTC #SiteReliability #PlatformEngineering #TechPodcast #FexingoBusiness #BusinessPodcast #DevOpsDaily #SoftwareOperations Keep every episode free: buymeacoffee.com/fexingo