afdesk

> Just thinking out loud how to test this change: As part of our integration tests, we can specify the new PV resource and have it get scanned and create...

@simar7 could you take a look at this PR when you have time? also it'd be nice if you try to run it locally. thanks

@simar7 is there something strange in the logs? in my env I see `OOMKilled` on Minikube ```sh {"level":"error","ts":"2025-09-09T14:34:43+06:00","logger":"reconciler.scan job","msg":"Scan job container","job":"trivy-system/scan-vulnerabilityreport-98b66b69","container":"88e558cf-97c8-41a1-a5b3-da6e6f076d73","status.reason":"OOMKilled","status.message":"------------------>_] 97.69% 6.13 MiB p/s ETA 0s68.98 MiB / 70.12...

> just took another look at it - wouldn't changing the test image impact any assertions that we make? It seems that there's no updated test / broken test as...

@dependabot recreate

> the operator is constantly scanning the same image across different namespaces. @mleykin-squarespace I suggest `secret` scanner is enabled in your env, so all scans happen on client side and...

@marcofranssen thanks a lot for your contribution! we really appreciate it `e2e-test` is failed twice, do you understand a reason? also, it looks like `BREAKING CHANGE`, so we need to...

> Is the failure really only on this PR or is it something that happens on all PRs at the moment? i've created a simple PR and the tests are...

@marcofranssen I took a quick look at the error the e2e test doesn't get a report in client - server mode. I also see, that it uses `global.imageRegistry`. so I'd...

@marcofranssen thanks for your efforts! we appreciate it! now Simar is on vacation, so let's wait for his opinion pls