Chip Zoller
Chip Zoller
Ok, was worth a try. What do you think, @onweru ?
Related to comment [here](https://github.com/kyverno/kyverno/issues/1810#issuecomment-821561846).
Yes, that is a bad mutation rule. However, I have also noticed something. With the following ClusterPolicy, Kyverno appears to be doing at least some validation of the schema: ```yaml...
>do we expect a validation error here? Yes, we do, because it's the exact same contents otherwise.
This issue is still about producing some error on a resource if it cannot be mutated somehow. I don't know what all those conditions may be, but one of them,...
Ok, didn't think about that. I guess that was a bad example. We can still write an error event if other mutations fail on a resource, I just don't know...
It appears so. You should first verify the issue still exists in the present state of `main` branch.
What steps did you take to attempt to determine this is the case?
You do not need to keep mentioning maintainers on issues/PRs where they are already engaged. I'm asking about what steps you followed to verify that this is still a gap...
This isn't about creating a policy which is invalid but the failed attempts of a mutation by that policy.