Skip to content

feat: StartDateTime and EndDateTime, Timezones for NodePool Disruption Budgets #1446

Closed as not planned
@ant-smith

Description

@ant-smith

Description

What problem are you trying to solve?

As apart of planned events, there are instances in which budgets should be schedule-able within a human readable format that can be easily understood and reasoned about.

This feature should also follow the current standard of minimal ("most restrictive") budgeting when multiple budgets are defined with overlapping timeframes or crontab schedules.

How important is this feature to you?

This feature would enable operators to schedule budgets for many one-off events in the future when they are known about, without having to create and compare complex crontab definitions against one another.

  • 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

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/featureCategorizes issue or PR as related to a new feature.lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.needs-triageIndicates an issue or PR lacks a `triage/foo` label and requires one.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions