-
Notifications
You must be signed in to change notification settings - Fork 892
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Introduce a mechanism to actively trigger rescheduling #4840
Comments
We need a document for this feature that is missing from this umbrella issue. |
FYI |
/close |
@RainbowMango: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
What would you like to be added:
Introducing a mechanism of actively triggering rescheduling.
Why is this needed:
Proposal of introducing a rebalance mechanism to actively trigger rescheduling of resource.
Assuming the user has propagated the workloads to member clusters, in some scenarios the current replicas distribution
is not the most expected, such as:
Aggregated
schedule strategy, replicas were initially distributed across multiple clusters due to resourceconstraints, but now one cluster is enough to accommodate all replicas.
Therefore, the user desires for an approach to trigger rescheduling so that the replicas distribution can do a rebalance.
The issue is created to track all related activities:
Proposal:
Implementation:
Webhook: Introduce a validation webhook to prohibit WorkloadRebalancer from being modified #4859UT
E2E Test:
Doc of Best Practice:
The text was updated successfully, but these errors were encountered: