Ha Son Hai
Ha Son Hai
I would like to add more info: Increasing CPU limit to 5 not help much. the first 6 hours with 2 cores, 1000 images scanned later in 10 hours with...
We did the same deploy of the scanner on a different cluster. This cluster is bigger but the Harbor Registry that runs on it has only ~1200 images. The CPU...
I think, based on this document: https://aquasecurity.github.io/trivy/v0.30.4/docs/references/customization/envs/ We can try with TRIVY_SECURITY_CHECKS="vuln".
> @hasonhai Were you able to test it out? It doesn't look like setting that env variable would pass it onto the container running trivy A member in my team...
Hi! Did you found the issue of this query?
I encounter the same issue. Is there any solution but removing the tls from ingress config?
One of the error may be you forgot to set "spec.clusterIP: None" in the service file.
I have a similar issue. When executing into the container, I cannot invoke nvidia-smi. ```bash []$ kubectl exec -it nvidia-device-plugin-daemonset-hsxjh -- bash [root@nvidia-device-plugin-daemonset-hsxjh /]# nvidia-smi Failed to initialize NVML: Insufficient...
I found the error. I have to disable selinux in crio.conf to have it works.