Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Its not mandatory for trivy to have persistant volume #1048

Open
Vad1mo opened this issue Sep 10, 2021 · 4 comments
Open

Its not mandatory for trivy to have persistant volume #1048

Vad1mo opened this issue Sep 10, 2021 · 4 comments

Comments

@Vad1mo
Copy link
Member

Vad1mo commented Sep 10, 2021

As Trivy CVS DB is relatively small, it can be downloaded on each pod start from the internet.

It would be good if this helm chart would have the option:

persistence.trivy.enabled

When enabled is set to false the chart should use a emptyDir instead of an PVC.

@ninjadq
Copy link
Member

ninjadq commented Sep 16, 2021

why we need this option for trivy? In what scenario we must want this?

@Vad1mo
Copy link
Member Author

Vad1mo commented Nov 3, 2021

the reason to not use a PVC is to have stateless Trivy setup, (less overhead, more flexible setup) it most cases it is ok to always download the DB on pod restart (the DB is currently around ~130MB)

@slushysnowman
Copy link

This should be relatively easy to implement and would be a big bonus - we've just swapped to using EFS in AWS to get around this, but there's no reason why Trivy can't be stateless - but because persistence is enabled at top level, not fine-grained per workload, it makes it hard to achieve this, if for example you do want persistence enabled for the jobservice

Copy link

github-actions bot commented Feb 8, 2024

This issue is being marked stale due to a period of inactivity. If this issue is still relevant, please comment or remove the stale label. Otherwise, this issue will close in 30 days.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants