fix: [NPM] add NetworkPolicy validation for matchExpression values #1717
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.
Issue
Kubernetes doesn't validate matchExpression label values in NetworkPolicies. Currently, NPM may log an uninformative error for non-standard matchExpression labels.
We should validate matchExpression labels during translation and error with a clear message if necessary.
Details
The issue can occur for any use of matchExpression values (used with the
InorNotInoperator). This includes:Example NetworkPolicy (passes
kubectlvalidation):Typical k8s validation for labels in
matchLabels:Current, uninformative error from NPM: