Kubernetes CronJob Not Triggering with Timezone Configuration in 1.25
I'm maintaining legacy code that I've looked through the documentation and I'm still confused about I'm experiencing issues with a Kubernetes CronJob that I set up to run a job at a specific time every day... I've configured the CronJob to use a timezone, but it seems like the job is not triggering as expected. I initially defined the CronJob like this: ```yaml apiVersion: batch/v1beta1 kind: CronJob metadata: name: my-cronjob spec: schedule: "0 15 * * *" jobTemplate: spec: template: spec: containers: - name: my-container image: my-image:latest command: ["/bin/sh", "-c", "echo Hello World"] restartPolicy: OnFailure ``` I expected this job to run every day at 3 PM UTC. However, it seems that it is not triggering at all. I verified the Kubernetes version is 1.25, and I even checked the logs of the controller manager for any related messages but couldn't find anything useful. To troubleshoot, I tried changing the schedule to a more immediate time, like "* * * * *" to see if it would trigger every minute, but still no luck. I also checked the Kubernetes documentation, and it mentions that the schedule is in UTC by default, but Iām not sure how to handle timezone adjustments properly in this case. I also tried adding the timezone annotation: ```yaml apiVersion: batch/v1beta1 kind: CronJob metadata: name: my-cronjob annotations: kubernetes.io/cron-job-timezone: "America/New_York" ``` I expected this to adjust the timing to my local timezone, but it still does not seem to trigger. Is there an scenario with my configuration, or is there a known bug in this version that could be affecting CronJobs with timezone settings? Any insights or suggestions would be greatly appreciated! My development environment is Windows. I'd really appreciate any guidance on this. Is there a better approach? What would be the recommended way to handle this?