Due to a bad update on our side, some CronJob on AWS/EKS may have resulted in being scheduled in the local timezone of the cluster, instead of the UTC timezone.
During the next deployment of your CronJob, UTC timezone will be enforced as it was intended.
If you require precise timing in the execution of your cronjob, please be sure to check the scheduling time is correct before re-deploying.
Note: We plan to support specific timezone in CronJob in a future release.
Regards,
Romain from Qovery