We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
1.12
1.28
Other (specify in description)
When deploy policies using Kyverno-policies helm chart 3.2.5 I can see Chart.yaml is specified kubeVersion: '>=1.25.0-0' and appVersion: v1.12.5.
When I view effective yaml of policies I see:
kyverno.io/kyverno-version: 1.6.0 policies.kyverno.io/minversion: 1.6.0 kyverno.io/kubernetes-version: "1.22-1.23"
There is no value I can change this.
I would like to have a value in values.yaml using which I can control this behavior
No response
The text was updated successfully, but these errors were encountered:
Thanks @sergey198828 for creating the issue.
kyverno.io/kyverno-version: 1.6.0 should be updated upon each new Kyverno release. Feel free to raise a PR for the fix.
kyverno.io/kyverno-version: 1.6.0
kyverno.io/kubernetes-version: "1.22-1.23" should be the Kubernetes versions we tested and verified, they don't seem to be updated though.
kyverno.io/kubernetes-version: "1.22-1.23"
Sorry, something went wrong.
Thanks @realshuting, opened Pull request. kyverno/kyverno#11258
Successfully merging a pull request may close this issue.
Kyverno Version
1.12
Kubernetes Version
1.28
Kubernetes Platform
Other (specify in description)
Description
When deploy policies using Kyverno-policies helm chart 3.2.5 I can see Chart.yaml is specified kubeVersion: '>=1.25.0-0' and appVersion: v1.12.5.
When I view effective yaml of policies I see:
There is no value I can change this.
Steps to reproduce
Expected behavior
I would like to have a value in values.yaml using which I can control this behavior
Screenshots
No response
Kyverno logs
No response
Slack discussion
No response
Troubleshooting
The text was updated successfully, but these errors were encountered: