-
Notifications
You must be signed in to change notification settings - Fork 276
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
Exclude non-ready nodes from scheduling. #3413
Exclude non-ready nodes from scheduling. #3413
Conversation
/ok-to-test |
✅ Deploy Preview for kubernetes-sigs-kueue canceled.
|
/assign @mimowo |
I am on the integration tests failure |
bfdf1f8
to
275a18a
Compare
/retest |
1 similar comment
/retest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm, just nits
d230cc6
to
b1ef2cc
Compare
/retest |
b1ef2cc
to
dc4e2ef
Compare
/lgtm Thanks! |
LGTM label has been added. Git tree hash: 87f227e692d7b95f36db54f6c27aea0f5bea86c1
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/approve
I believe all comments are addressed
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mimowo, mszadkow The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
* Exclude non-ready nodes from scheduling. * Update after code review * Move TAS indexer to subpackage * Use TAS indexer to filter out non ready nodes * Update integration tests * Update to match verify
What type of PR is this?
/kind feature
What this PR does / why we need it:
Non-ready nodes are excluded by kube-scheduler so including them in TAS can be considered a bug - they will not be able to use in practice, and the pods will not schedule.
Which issue(s) this PR fixes:
Fixes #3401
Special notes for your reviewer:
Does this PR introduce a user-facing change?