You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, CronJob schedule expressions are all considered to be UTC, except for in-pod cron jobs which follow the timezone of the service
For one of our projects, we'd like to run a specific cron just after midnight (local time). But we cannot configure that, since this expression does not considers daylight saving time. 0 23 * * * will run at 00:00 AM CET or 01:00 CEST.
Timezones:
The default timezone for cron jobs is UTC.
Native cron jobs use the timezone of the node, which is UTC.
In-pod cron jobs use the timezone of the defined service, which can be configured to something other than UTC.
The only problem is that if the timezone is set, and the frequency means it lands as an in-pod cronjob, we won't do anything with the timezone. We can document this as a caveat though. The addition of the field seems simple enough though, will see what the rest of the team thinks.
Currently, CronJob schedule expressions are all considered to be UTC, except for in-pod cron jobs which follow the timezone of the service
For one of our projects, we'd like to run a specific cron just after midnight (local time). But we cannot configure that, since this expression does not considers daylight saving time.
0 23 * * *
will run at 00:00 AM CET or 01:00 CEST.https://docs.lagoon.sh/concepts-basics/lagoon-yml/#cron-job-example
Kubernetes supports CronJob syntax with timezone support since v1.27: https://kubernetes.io/docs/concepts/workloads/controllers/cron-jobs/#time-zones
Can you support specifying a time zone for CronJobs in
.lagoon.yml
?The text was updated successfully, but these errors were encountered: