[Bug] Kyverno Reports Controller collides with other policy engines installed on the same cluster

[szimonek]

Kyverno Version

1.12.0

Description

Hi,

I have installed two policy engines on one K8s cluster: Kyverno and Kubewarden. They can coexist together without collision in every aspect but not PolicyReports. After Kuberwarden generates its set of PolicyReport objects (apiVersion: wgpolicyk8s.io/v1alpha2) Kyverno can't generate its own PolicyReports and reports-controller pods starts to log a lot of messages such as:

2024-05-13T17:18:21.730185223+02:00 2024-05-13T15:18:21Z	ERROR	aggregate-report-controller.worker	controller/run.go:128	Failed to process request	{"id": 6, "obj": "app-qpal/02f31e19-2c01-4a0f-b35f-346cce8ea7d7", "error": "can't delete report because it is not managed by kyverno"}
2024-05-13T17:18:21.833979726+02:00 2024-05-13T15:18:21Z	ERROR	aggregate-report-controller.worker	controller/run.go:128	Failed to process request	{"id": 7, "obj": "app-qpal/969e4c0f-406a-4873-b2a6-0e21329ec8a6", "error": "can't delete report because it is not managed by kyverno"}
2024-05-13T17:18:21.929613702+02:00 2024-05-13T15:18:21Z	ERROR	aggregate-report-controller.worker	controller/run.go:128	Failed to process request	{"id": 3, "obj": "app-test/dccc901b-ba5a-4aca-b646-7f0cfd83d517", "error": "can't delete report because it is not managed by kyverno"}

When I uninstalled Kubewarden and deleted its PolicyReport objects, Kyverno started to generate its own PolicyReports without any problem.

Expected behavior is that these two engines can fully coexist in one k8s cluster.

Best regards
Szymon

Slack discussion

No response

Troubleshooting

• I have read and followed the documentation AND the troubleshooting guide.
• I have searched other issues in this repository and mine is not recorded.

[welcome]

Thanks for opening your first issue here! Be sure to follow the issue template!