Trivy server with self signed certificate fails in starboard-operator
dirien opened this issue · comments
What steps did you take and what happened:
At my company, we run the Trivy Server with our internal Company PKI. This, ofc, appear for the Trivy in starboard as signed by an unknown authority (x509 certificate signed by unknown authority)
Trivy (>0.24.2) has the flag --insecure (env: TRIVY_INSECURE) to allow insecure server connections when using SSL.
The starboard-operator should be able to handle this.
What did you expect to happen:
We can set a flag to enable unsecure trivy remote server.
Anything else you would like to add:
I create a PR for this.
Environment:
- Starboard version (use
starboard version): 0.14.1 - Kubernetes version (use
kubectl version): > 1.20 - OS (macOS 10.15, Windows 10, Ubuntu 19.10 etc):