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

[proposal] koord-descheduler: Optimize the reassessment of single-node resource left #2119

Open
zwForrest opened this issue Jun 27, 2024 · 1 comment
Labels
kind/proposal Create a report to help us improve

Comments

@zwForrest
Copy link
Contributor

What is your proposal:
Currently, during eviction in rescheduling, only the total cluster resources are considered to determine if they are sufficient for the pod being rescheduled, without taking into account whether single nodes have the required resources.

Why is this needed:
Prevent the scenario where other nodes become hotspots after rescheduling.

Is there a suggested solution, if so, please add it:

@zwForrest zwForrest added the kind/proposal Create a report to help us improve label Jun 27, 2024
@songtao98
Copy link
Contributor

Nice proposal! koord-descheduler re-uses the NodeFit pre-check logic of Kubernetes Descheduler's DefaultEvictor. This is not enough in all real cases. Other optimization to NodeFit includes like TopologySpreadConstraints and so on. We'll continue to improve this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/proposal Create a report to help us improve
Projects
None yet
Development

No branches or pull requests

2 participants