Chip Zoller
Chip Zoller
I ended up just changing the version info in the chart metadata file to reflect the latest chart release.
That's fine, let's update whatever tests fail in this PR to have the new "correct" result. Speaking of this specific test ([allowed-label-changes](https://github.com/kyverno/policies/tree/main/other/allowed-label-changes)), I'm not even sure how we're testing UPDATE...
The value of the RESULT column in the test output is always `Pass` when the tested outcome matches the outcome stated in the test manifest's `results[].result` field. If this field...
For code-level questions it's best to work with @realshuting or @eddycharly.
Further reading: https://argo-cd.readthedocs.io/en/latest/user-guide/sync-options/
This issue requires using server side apply captured in #3800
Does it work if you remove the `metadata.namespace` field from the ClusterPolicy?
Thanks. Given that adding a `namespace` field to a cluster-scoped resource is valid in Kubernetes (it will be disregarded), it's arguable this should be considered a "bug" but I agree...
In the future, please use either a discussion or issue, not both. This may not be a bug but how strategic merge patches work in this section if there is...
This was already done in https://github.com/kyverno/kyverno/pull/10521