👀 Views: 19 💬 Answers: 1 📅 Created: 2025-06-17

kubernetes cronjob timezone YAML

I'm relatively new to this, so bear with me. I'm collaborating on a project where I'm stuck on something that should probably be simple... I'm trying to set up a Kubernetes CronJob that is supposed to run every day at 3 AM UTC. However, it's not executing at the expected time, and I'm beginning to suspect it might be related to timezone settings either on the server or within the CronJob itself. Here's the configuration I have in my `cronjob.yaml`: ```yaml apiVersion: batch/v1beta1 kind: CronJob metadata: name: my-cronjob spec: schedule: "0 3 * * *" jobTemplate: spec: template: spec: containers: - name: my-container image: my-image:latest command: ["/bin/sh", "-c", "echo Hello, World!"] restartPolicy: OnFailure ``` I expected it to run at 3 AM UTC every day, but instead, it seems to be executing at 4 AM UTC. I've checked the timezone of the Kubernetes nodes and they are set to UTC. I also verified that the container itself is running in UTC by executing `date` within the container, which returns the expected timezone. To troubleshoot, I tried modifying the schedule to `"0 2 * * *"` to see if it would shift the execution time by an hour, but it still executed at 4 AM. Additionally, I checked the Kubernetes events using `kubectl get events --sort-by=.metadata.creationTimestamp` and found no issues or errors related to the CronJob. Is there a possibility that Kubernetes is interpreting the schedule based on a different timezone setting? How can I ensure that the CronJob runs exactly at 3 AM UTC as intended? Any insights would be greatly appreciated! This is part of a larger service I'm building. Is there a better approach? Any help would be greatly appreciated! I'm coming from a different tech stack and learning Yaml. What's the correct way to implement this? Any ideas how to fix this?