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

【community bridge】Pick out reasonable victim pods for rescheduling plugin #2425

Closed
Thor-wl opened this issue Aug 11, 2022 · 5 comments
Closed
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@Thor-wl
Copy link
Contributor

Thor-wl commented Aug 11, 2022

As what Rescheduling Desgin Doc says and rescheduling plugin implemented currently, it is a little bit rough to evict selected victims without difference. In fact, we should consider more factors such as pod priority, critical pod and so on. In order to make rescheduling reasonable, your tasks are as follows.

  • Provide a complete design with documentation.
  • Implement the design align with code of conduct.
  • Provide a full test in classical scenarios with UT and E2E.

mentor: Thor-wl

@Thor-wl Thor-wl added the kind/feature Categorizes issue or PR as related to a new feature. label Aug 11, 2022
@Thor-wl Thor-wl changed the title 【community bridge】Enhancement to Rescheduling 【community bridge】Pick out reasonable victim pods for rescheduling plugin Aug 11, 2022
@rainstarwz
Copy link

@Thor-wl Hi ! I'm interested in this issue. Let me know what should I do?

@Thor-wl
Copy link
Contributor Author

Thor-wl commented Aug 17, 2022

@Thor-wl Hi ! I'm interested in this issue. Let me know what should I do?

Great. Please send me a brief resume.

@0saurabh0
Copy link

0saurabh0 commented Aug 20, 2022

Hi @Thor-wl I would love to work on this. Anything for getting started ?
I've applied for this project in this term of LFX mentorship and also I've sent you my resume as mentioned.

@stale
Copy link

stale bot commented Dec 3, 2022

Hello 👋 Looks like there was no activity on this issue for last 90 days.
Do you mind updating us on the status? Is this still reproducible or needed? If yes, just comment on this PR or push a commit. Thanks! 🤗
If there will be no activity for 60 days, this issue will be closed (we can always reopen an issue if we need!).

@stale stale bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 3, 2022
@stale
Copy link

stale bot commented Mar 23, 2023

Closing for now as there was no activity for last 60 days after marked as stale, let us know if you need this to be reopened! 🤗

@stale stale bot closed this as completed Mar 23, 2023
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. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

3 participants