-
Notifications
You must be signed in to change notification settings - Fork 963
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】Implement pod filter chain for rescheduling #2428
Comments
Hello Sir, I am Rishabh, an undergraduate computer engineering student at Delhi Technological University. I am interested in this project of Mentorship of LFX. Can you please share further information? How can we be selected for mentorship and also contribute to this project? Skills: C, C++, Python, Golang (Intermediate) Thanks & Regards |
@anonymousr007 Hi. Please send a resume to me. My email is [email protected]. Thanks. |
Hello sir, I sent my resume to you. Thanks. |
OK. Received. Thanks. |
Please share further information. Thanks. |
Hello Sir, I submitted my cover letter and resume to the official LFX Mentorship Portal. Please share some tasks or some resources to learn more about this project. Thanks. |
Hello 👋 Looks like there was no activity on this issue for last 90 days. |
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! 🤗 |
As what Rescheduling Desgin Doc says and #2184 implemented currently, all pods will be regared as potential victims. It is not so reasonable for some scenarios. For example, team1 and team2 share a k8s cluster and each team maps to a queue(queue1 and queue2). They want to run their own business without interference. If team1 enables rescheduling, only pods in queue1 should be regared as potential victims. In order to do that, your tasks are as follows.
mentor:Thor-wl
The text was updated successfully, but these errors were encountered: