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
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:
replicas migrated due to cluster failover, while now cluster recovered.
replicas migrated due to application-level failover, while now each cluster has sufficient resources to run the replicas.
as for Aggregated schedule strategy, replicas were initially distributed across multiple clusters due to resource
constraints, 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:
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: