You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Installed trivy-operator 0.22.0 with helm chart version 0.24.1 with the following set in my values.yaml (copy-pasted and uncommented from the chart's default values)
The scan-vulnerabilityreport-* Jobs created do contain the custom volume, but it's been converted to an emptyDir. the custom volume mount is missing from both the container and the initContainer:
I don't see any relevant errors or warnings in the trivy-operator logs (grepped for "custom", "volume", and "mount", case-insensitive).
What did you expect to happen:
I expected the Job's var-lib-etcd volume to be a hostPath, and the container and initContainer volumeMounts to mount the var-lib-etcd volume.
Anything else you would like to add:
N/A
Environment:
Trivy-Operator version (use trivy-operator version): 0.22.0
Kubernetes version (use kubectl version): 1.28.7
OS (macOS 10.15, Windows 10, Ubuntu 19.10 etc): Ubuntu 20.04
The text was updated successfully, but these errors were encountered:
What steps did you take and what happened:
Installed trivy-operator 0.22.0 with helm chart version 0.24.1 with the following set in my values.yaml (copy-pasted and uncommented from the chart's default values)
The scan-vulnerabilityreport-* Jobs created do contain the custom volume, but it's been converted to an emptyDir. the custom volume mount is missing from both the container and the initContainer:
I don't see any relevant errors or warnings in the trivy-operator logs (grepped for "custom", "volume", and "mount", case-insensitive).
What did you expect to happen:
I expected the Job's var-lib-etcd volume to be a hostPath, and the container and initContainer volumeMounts to mount the var-lib-etcd volume.
Anything else you would like to add:
N/A
Environment:
trivy-operator version
): 0.22.0kubectl version
): 1.28.7The text was updated successfully, but these errors were encountered: