Skip to content
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

Wildcards in match / exclude statements should be invalid #1963

Closed
chipzoller opened this issue Jun 4, 2021 · 2 comments · Fixed by #2137
Closed

Wildcards in match / exclude statements should be invalid #1963

chipzoller opened this issue Jun 4, 2021 · 2 comments · Fixed by #2137
Assignees
Labels
enhancement New feature or request

Comments

@chipzoller
Copy link
Member

chipzoller commented Jun 4, 2021

If we're not going to support wildcards (*) in match / exclude statements, then Kyverno needs to detect them and reject the policy as being invalid.

@chipzoller chipzoller added the enhancement New feature or request label Jun 4, 2021
@hans-d
Copy link

hans-d commented Jul 13, 2021

a way to specify ALL kinds, or not being forced to specify at least 1 kind would be good imho.

Eg:

  • All resources created by role X should have label Y=Z.
  • In the case of cli usage only, I want to validate that no resource has a label A=B

@JimBugwadia
Copy link
Member

See: #1954 and #1981.

Its possible to support an "all kinds", and there seem to be some good use cases for that, but as discussed in the referenced issues there are feature and performance tradeoffs we will need to navigate carefully.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants