afdesk
afdesk
Hi @salmannaseempb thanks for the report! Is this issue repeatable?
Hi @rkeidar it seems it's a known issue in Trivy https://github.com/aquasecurity/trivy/issues/5003 and there is a fix, but it hasn't merged yet https://github.com/aquasecurity/trivy/pull/6405/ wdyt?
the next trivy release should have the fix )
Hi guys! sorry for long delay. @chit4 @gnadaban Could you confirm that this issue is still relevant with the latest version (v0.23.0, Helm chart v0.25.0)? thanks!
I've retested this case in several environments, this feature should work as expected with the latest version (v0.23.0, Helm chart v0.25.0). Please feel free to reopen this issue, if it...
@badgerspoke thanks for the report could you try with a tag `:1`: `/aquasecurity/trivy-checks:1` instead of `/aquasecurity/trivy-checks:0`?
@badgerspoke I meant could you update `trivy-checks` with the latest tag - `1`? the current Trivy operator depends on the current Trivy, and it needs `trivy-checks:1`. cc @simar7, is it...
There is a small test with Trivy directly: ```sh $ trivy clean --all $ trivy config --checks-bundle-repository mirror.gcr.io/aquasec/trivy-checks:0 . 2025-03-18T11:00:51+06:00 INFO [misconfig] Misconfiguration scanning is enabled 2025-03-18T11:00:51+06:00 INFO [misconfig] Need...
> All was well initially - scans used it and ran fine - but today I see this in the operator logs: This error comes from Trivy. it looks like...
> The token will expire, this is normal and expected behaviour for IRSA in AWS. The token is mounted into the pod automatically so is it possible the operator only...