-
Notifications
You must be signed in to change notification settings - Fork 38.7k
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
Update PreFilter interface to return a PreFilterResult #108648
Conversation
@ahg-g: This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the The 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/test-infra repository. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ahg-g 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 |
c9900f1
to
e53b90d
Compare
/assign @alculquicondor @Huang-Wei |
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.
good for squash
squashed into two commits. I had to remove the underscore from "node_x" names in the affinity tests because they were causing issues with |
/lgtm |
/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.
Pretty neat! Just one nit, LGTM otherwise.
…rms; if exist, the pod is only evaluated against the matching nodes.
/hold cancel |
/lgtm |
/lgtm still |
/cc @MaciekPytel @x13n |
What type of PR is this?
/kind feature
What this PR does / why we need it:
Updates the scheduler framework's PreFilter interface to return a new type named PreFilterResult; this allows PreFilter to influence which nodes to evaluate downstream (Filter and beyond).
The first plugin to use this is NodeAffinity which looks for node.Name MatchField terms; if exist, the pod is only evaluated against the matching nodes
This can be extended to also influence the number of nodes to score, but that is left for the future.
Which issue(s) this PR fixes:
Part of ##108606
Special notes for your reviewer:
Does this PR introduce a user-facing change?