feat: add support for matchExpressions when filtering for nodes #1697
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description, Motivation and Context
Includes the ability to use a Kubernetes
matchExpressions
label selector for thenodeResources
analyzer.I wanted to write pre-flight checks to analyze nodes that contained a specific label and another that negated it. Currently, this is not possible with the
MatchLabel
selector. It would be possible with aMatchExpressions
label selector by using the negation operators (e.g.,NotIn
/DoesNotExist
)Checklist
Does this PR introduce a breaking change?