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
I’d like to request the addition of a timeZone option for scheduled Spark jobs in the Spark Operator. Starting with Kubernetes 1.25, the timeZone field is supported in CronJobs, allowing users to specify the timezone for scheduling. However, this feature does not currently appear to be supported in the Spark Operator’s scheduled job configuration.
This omission makes it challenging to manage Spark job schedules in multi-timezone environments. Users have to resort to workarounds, such as adjusting schedules manually or modifying their application logic, which can be error-prone and less intuitive compared to native timezone support.
It would be great if the Spark Operator could include support for timeZone, aligning with Kubernetes’ native CronJob capabilities. This addition would enhance usability and make scheduling Spark jobs more straightforward and consistent with Kubernetes standards.
Looking forward to hearing your thoughts on this! Please let me know.
Additional context
No response
Have the same question?
Give it a 👍 We prioritize the question with most 👍
The text was updated successfully, but these errors were encountered:
What question do you want to ask?
I’d like to request the addition of a timeZone option for scheduled Spark jobs in the Spark Operator. Starting with Kubernetes 1.25, the timeZone field is supported in CronJobs, allowing users to specify the timezone for scheduling. However, this feature does not currently appear to be supported in the Spark Operator’s scheduled job configuration.
This omission makes it challenging to manage Spark job schedules in multi-timezone environments. Users have to resort to workarounds, such as adjusting schedules manually or modifying their application logic, which can be error-prone and less intuitive compared to native timezone support.
It would be great if the Spark Operator could include support for timeZone, aligning with Kubernetes’ native CronJob capabilities. This addition would enhance usability and make scheduling Spark jobs more straightforward and consistent with Kubernetes standards.
Looking forward to hearing your thoughts on this! Please let me know.
Additional context
No response
Have the same question?
Give it a 👍 We prioritize the question with most 👍
The text was updated successfully, but these errors were encountered: