afdesk
afdesk
hi @sudheer-talamanchi could you try to add something like next settings to the config map? ```yaml trivy.configFile: | image: platform: linux/arm64 ```
@sudheer-talamanchi it seems you use the old version ```yaml app.kubernetes.io/name: trivy-operator app.kubernetes.io/version: 0.26.1 ``` could you re-check with the latest version (v0.29)?
Hi @sudheer-talamanchi ! now there is another issue here ```yaml trivy.tag: v0.29.0 ``` it's a tag for Trivy, not for trivy-operator. the current version of Trivy is v0.67, v0.29 is...
That’s definitely better — these are now logged at the `info` level instead of `error`, which is an improvement 🙂 Are the other reports showing up now? It’s quite possible...
> Will this image push the findings to security HUB do you have a concern about telemetry? https://trivy.dev/docs/latest/advanced/telemetry/ trivy v0.29.0 is a really old version, so no, it doesn't support...
@daanschipper thanks for the contribution!
@alexander-dammeier thanks for the report! could you pls try to set `scanJob.compressLogs` to `false`?
Hi guys! sorry i missed this thread. at first could you confirm that you tried to write a custom policy? https://aquasecurity.github.io/trivy-operator/latest/tutorials/writing-custom-configuration-audit-policies/
> [@afdesk](https://github.com/afdesk) Will a solution for this problem be implemented in version 0.31.0? I hope - yes, we'll try to clarify this issue before v0.31.0
@xzizka thanks for the report! could you check it with the latest Trivy operator, that contains the latest Trivy?