Chip Zoller
Chip Zoller
Don't know what that means.
Yes, that is what I was suggesting, just didn't know it was called lazy evaluations.
>Currently, you cannot use {{request.object.xxxxxx}} into context without breaking the DELETE operation: You can, you just need to use a [non-existence check](https://kyverno.io/docs/writing-policies/jmespath/#non-existence-checks). ``` jmesPath: request.object.metadata.labels."clusterresourcequota" || '' ```
I believe this should now be possible today in a couple ways: 1. preconditions can be used inside a `foreach` loop statement to perform similar logic without having to know...
This has been fixed. Testing on 1.11.3 shows that triggering resources may have colons in their names. ```yaml apiVersion: kyverno.io/v1 kind: ClusterPolicy metadata: name: crossplane-aws-rolebinding spec: rules: - name: role-arn-to-serviceaccount...
Can you give us a hint so we can add something to the documentation?
Since what you're doing isn't really what this issue describes, maybe just point to the Vault docs if they exist?
You can self assign issues.
This is old and stale, possibly no longer an issue. Closing. If this is still observed with later versions of Kyverno (1.11 is the current release as of now), please...
Closed in 1.10 by PR #6658