Skip to content
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

Closed
chaosi-zju opened this issue Apr 17, 2024 · 4 comments
Closed

Introduce a mechanism to actively trigger rescheduling #4840

chaosi-zju opened this issue Apr 17, 2024 · 4 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Milestone

Comments

@chaosi-zju
Copy link
Member

chaosi-zju commented Apr 17, 2024

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:

  • 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:

Proposal:

Implementation:

UT

E2E Test:

Doc of Best Practice:

@RainbowMango
Copy link
Member

We need a document for this feature that is missing from this umbrella issue.

@RainbowMango
Copy link
Member

FYI
Add two tasks for the zh documents.

@RainbowMango
Copy link
Member

/close
since all tasks have been addressed.

@karmada-bot
Copy link
Collaborator

@RainbowMango: Closing this issue.

In response to this:

/close
since all tasks have been addressed.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
Status: Planned In Release 1.10
Development

No branches or pull requests

3 participants