Pipelines: Cron Scheduler timezone is set to always be UTC, should be local timezone for the cluster

[NikeNano]

What happened:
When scheduling a pipeline using a cron expression the job are not run on the expected time. The hours are not aligned between the displayed time in the UI(correct time and local timezone in my case) and the execution of the cron jobs.

What did you expect to happen:
I was expecting the cron job to be executed at 10:15 when i set it to
0 15 10 * * ?, this is not the case. Instead i have to set this to 0 15 9 * * ?. I seams to be a difference in the set timezones....

What steps did you take:
I have scheduled a Kubeflow pipeline to execute once a day using the UI, editing the cron expression.

Anything else you would like to add:
Happy to make a contribution if this is something that needs to be fixed :)

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[Bobgy]

duplicate of https://github.com/kubeflow/pipelines/issues/3935

let's track in the new issue because it has more accurate information

[Bobgy]

Sorry for wrong dup

[NikeNano]

Based upon the findings presented in https://github.com/kubeflow/pipelines/issues/3935 should we move towards using time timezones or stay on using Unix timestamp and shift the cron schedules to UTC? Is it also worth allowing users to set the timezone as a parameter instead of using the local cluster timezone, but default to the cluster timezone? @Bobgy

[Bobgy]

Sounds reasonable moving towards local timezones + config.

Note, we might be refactoring the implementation to use K8s cronjobs in the future, so it's better align with their behavior.

[NikeNano]

Sounds reasonable moving towards local timezones + config.

Note, we might be refactoring the implementation to use K8s cronjobs in the future, so it's better align with their behavior.

Thanks for the feedback, great will do so!

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[kim-sardine]

Any progress with it? still have same issue

[Bobgy]

@kim-sardine this will be released in next KFP release

[hamko]

Hi, I tested this feature in 1.4.1 on GCP Marketplace, but looks not yet fixed. I set a periodic run trigger utc with the cron expression 0 57 12 * * ? and confirmed the corresponding run was triggered at 21:57 JST, displayed on the kubeflow dashboard UI (9 hours ahead of UTC). Do I misunderstand the fix #4641?

[NikeNano]

@hamko did you make any changes to the default settings in order to change the timezone for the scheduler? Currently the default is UTC to be backwards compatible, . For more info about the changes specifically to gcp_market place this PR refers to the file that sets it for gcp_market place. I have not used gcp_market place so will not be able to support you on the specific for it and how the deployment works in this case :(.