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
Scheduler PostFilter API #91547
Scheduler PostFilter API #91547
Conversation
/assign @lavalamp |
/retest |
This PR may require API review. If so, when the changes are ready, complete the pre-review checklist and request an API review. Status of requested reviews is tracked in the API Review project. |
/lgtm from sig-scheduling |
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
/lgtm |
/retest |
Friendly ping @lavalamp . It's a pure field addition to existing v1beta1 API, should be easy to review. |
/retest |
/approve In case you want to fix the nit: |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Huang-Wei, lavalamp 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 |
/lgtm |
/hold cancel |
@Huang-Wei: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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. I understand the commands that are listed here. |
/retest |
What type of PR is this?
/kind api-change
/kind feature
/sig scheduling
What this PR does / why we need it:
This PR introduced type
PostFilter
to scheduler component config API on version v1beta1.Which issue(s) this PR fixes:
Part of #91038.
Special notes for your reviewer:
Does this PR introduce a user-facing change?: