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, if quarkus.openshift.deployment-kind=CronJob, the deployed cronjob uses the default UTC timezone when scheduling jobs according to the quarkus.openshift.cron-job.schedule property. This is the case even when quarkus.openshift.env.vars.tz is set to a different time zone.
The command oc patch cronjobs app-name -p '{"spec": {"timeZone": "Time/Zone/Wanted" }}'
is needed after the deployment to change the time zone.
It would be great if a quarkus.openshift.cron-job.timezone property could be created that sets the cronjob time zone.
Implementation ideas
No response
The text was updated successfully, but these errors were encountered:
Description
Currently, if
quarkus.openshift.deployment-kind=CronJob
, the deployed cronjob uses the default UTC timezone when scheduling jobs according to thequarkus.openshift.cron-job.schedule
property. This is the case even whenquarkus.openshift.env.vars.tz
is set to a different time zone.The command
oc patch cronjobs app-name -p '{"spec": {"timeZone": "Time/Zone/Wanted" }}'
is needed after the deployment to change the time zone.
It would be great if a
quarkus.openshift.cron-job.timezone
property could be created that sets the cronjob time zone.Implementation ideas
No response
The text was updated successfully, but these errors were encountered: