What steps did you take and what happened:
When installing the trivy-operator we enable the alternateReportStorage which creates a PVC with accessMode set to ReadWriteOnce. This only allows a single pod to connect to the PVC which defeats the purpose of having it stored in alternateStorage because we are unable to start another pod to retrieve the JSON reports. If anything the accessMode should be configurable to allow us to set it to ReadWriteMany via a helm value.
What did you expect to happen:
The helm chart to have a configurable value option to set alternateReportStorage to ReadWriteMany so we can have multiple pods attach to the shared storage.
Anything else you would like to add:
This might also allow a CronJob to connect from time to time to clean up old reports as others have reported needs done.
Environment:
- Trivy-Operator version (use
trivy-operator version): 0.30.1
- Kubernetes version (use
kubectl version): 1.34.3
- OS (macOS 10.15, Windows 10, Ubuntu 19.10 etc): RHEL 9.7
What steps did you take and what happened:
When installing the trivy-operator we enable the alternateReportStorage which creates a PVC with accessMode set to ReadWriteOnce. This only allows a single pod to connect to the PVC which defeats the purpose of having it stored in alternateStorage because we are unable to start another pod to retrieve the JSON reports. If anything the accessMode should be configurable to allow us to set it to ReadWriteMany via a helm value.
What did you expect to happen:
The helm chart to have a configurable value option to set alternateReportStorage to ReadWriteMany so we can have multiple pods attach to the shared storage.
Anything else you would like to add:
This might also allow a CronJob to connect from time to time to clean up old reports as others have reported needs done.
Environment:
trivy-operator version): 0.30.1kubectl version): 1.34.3