Description

What problem are you trying to solve?
#943 made the deliberate decision to enforce UTC on all budget schedules. This is fine (since you can calculate to your specific timezone), until daylight savings time comes into play (depending on your region).

In our use case, we want to avoid node consolidation during working hours, since not all our workload is completely stateless. Currently, we either have to write suboptimal schedules, or we have to edit the schedules twice a year.

There should be a way to explicitly set the timezone. The original issue suggests adding a timezone field to the budgets; for our use case we would be happy if we could set it on the controller directly or to explicitly opt into using the nodes timezone.

How important is this feature to you?
Due to the way budgets currently work backwards to our use case (restricting disruptions instead of allowing them (ref: #1939 (comment))), this makes dealing with budgets even more complex, so we'd really like to see this.

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment