shuting
shuting
@vishal-chdhry - any updates on this one? Shall we keep it for 1.11.0?
Another ArgoCD related https://github.com/kyverno/kyverno/issues/11684.
@vishal-chdhry - any updates?
@vishal-chdhry - can you resolve conflicts?
Looks like a new sample policy to add, transferring the issue.
> What seems a little inconsistent is that `generateExisting` is required to catch a missed CREATE but not a missed UPDATE or DELETE. It seems like ALL those should be...
Attaching manifests for reproduction: 1. update the background controller env `BACKGROUND_SCAN_INTERVAL=2m` 2. create policy, note this policy doesn't use JMESPath variables which is to narrow down the issue, and generateExisting...
The issue still exists in 1.13.2.
> Thanks for reporting, if someone wants to fix this https://kubernetes.slack.com/archives/C0EG7JC6T/p1717485413210449 I'd love to give it a shot.
Hi @MichaelEischer - the force reconciliation (which happens every hour by default) should kick in and remediate this situation. Are you able to verify that?