bgoareguer
bgoareguer
@afdesk the problem was not about detecting the vulnerability but simply not showing the summary: Total: 0 (CRITICAL: 0)
It would be really cool if we could send the original report from the tool (trivy, kube-bench, kube-hunter, etc.) via Postee (cf https://github.com/aquasecurity/starboard/issues/899), intead of the report in the Starboard...
I like the current behavior of having the reports in same namespace as the resource they relate to. It makes it possible to use RBAC to restrict access to those...
Still present in Trivy 0.38.3 (for `trivy fs` only, not for `trivy image`)
@fgreinacher @JonasSchubert #322 has been merged. Can you please merge this PR?
The Kubernetes documentation on [probes](https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/) indicates that "A common pattern for liveness probes is to use the same low-cost HTTP endpoint as for readiness probes, but with a higher failureThreshold"....
Please also add a bullet point to publish the documentation (it seems to be a manual Github action and as of now, the currently published documentation does not include the...
The `trivy.dbRepository` parameter in the `helm/trivy/values.yaml` file also needs to be updated.
I had the same issue. Here is how I solved it: ``` DD_SOCIAL_AUTH_GITLAB_SCOPE: "read_api, read_user, openid, read_repository" ```
I would really like to activate duplicate deletion but I guess it would be safer to fix this issue first. Is there any investigation on this issue?