shuting

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/kubernetes-version: "1.22-1.23"` should be the...

> I would like to add ourselves to whatever list exists of people who would like this feature. > > We have exactly the same problem and the current approach...

>Do we need to add directly to Job object config [aka](https://github.com/kyverno/kyverno/blob/e004d8ae8d836b33741e28a97a25060f5c3d094f/charts/kyverno/templates/admission-controller/deployment.yaml#L108)? No need to. How did you upgrade Kyverno?

Were you upgraded from 1.11.x? I don't recall seeing such an issue while upgrading with Helm. Did you custom Kyverno installation? Can you please provide full steps for reproduction?

> @realshuting I’d be happy to take over and follow up on this work if needed. Yes @YTGhost - we need to adopt this change in Kyverno!

> As Kyverno version 1.13.0 was released, does this mean this has been completed ? Thanks. No, we rescheduled this to 1.14.0.

> Hi, just checking on this, I am getting an error where my appArmorProfile exclusion isn't being picked up - "kyverno-scan policy pod-pss-restricted/amazon-guardduty-exemptions fail: Validation rule 'amazon-guardduty-exemptions' failed. It violates...

What resource are you selecting in the policy? Can you share the policy please?

Does the policy work if you remove this? ``` clusterRoles: - namespace-owner ```

When you define a `clusterroles` in the `match` block it means only requests sent by the ClusterRole`namespace-owner` are processed.