-
Notifications
You must be signed in to change notification settings - Fork 38.9k
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
Removed no-empty validation of nodeSelectorTerm.matchExpressions. #62448
Conversation
/retest |
/cc @liggitt |
// if len(term.MatchExpressions) == 0 { | ||
// return append(allErrs, field.Required(fldPath.Child("matchExpressions"), "must have at least one node selector requirement")) | ||
// } | ||
|
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.
Remove rather than comment?
Nit on removing code rather than commenting it out… I don't anticipate this validation returning. LGTM otherwise, this makes the code behave as documented, and be forward compatible with field selector additions. A second from @kubernetes/api-reviewers would also be good. |
Signed-off-by: Da K. Ma <klaus1982.cn@gmail.com>
/retest |
cc @kubernetes/sig-scheduling-api-reviews |
ping @kubernetes/api-reviewers for comments, some other feature dependent on that PR :) |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: k82cn, liggitt 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 |
/retest |
[MILESTONENOTIFIER] Milestone Pull Request Needs Approval @k82cn @liggitt @kubernetes/sig-scheduling-misc Action required: This pull request must have the Pull Request Labels
|
/retest |
/retest Review the full test history for this PR. Silence the bot with an |
1 similar comment
/retest Review the full test history for this PR. Silence the bot with an |
/test all [submit-queue is verifying that this PR is safe to merge] |
/retest |
Automatic merge from submit-queue (batch tested with PRs 62448, 59317, 59947, 62418, 62352). If you want to cherry-pick this change to another branch, please follow the instructions here. |
Thanks. Can you pick this to 1.10 as well? |
@k82cn: 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. |
Automatic merge from submit-queue (batch tested with PRs 62982, 63075, 63067, 62877, 63141). If you want to cherry-pick this change to another branch, please follow the instructions <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md">here</a>. Removed e2e test on empty NodeAffinity. Signed-off-by: Da K. Ma <klaus1982.cn@gmail.com> **Which issue(s) this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close the issue(s) when PR gets merged)*: Fixes kubernetes#63027 **Special notes for your reviewer**: In kubernetes#62448, we removed the validation on empty `nodeAffinity` which is already handled in scheduler: select no objects. **Release note**: ```release-note None ```
Signed-off-by: Da K. Ma klaus1982.cn@gmail.com
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):part of #62002
Release note: