We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Trivy kubernetes scan takes a lot of time for small minikube cluster:
$ time trivy k8s --report summary --debug --disable-node-collector --timeout 30m0s 491,23s user 49,05s system 55% cpu 16:21,43 total
As said in #7661 Trivy fails even for test environment.
Trivy creates a new scanner for each kubernetes artifact:
trivy/pkg/k8s/scanner/scanner.go
Line 158 in ab3a3b2
Line 184 in ab3a3b2
As an idea we can try to optimize using of scanners.
$ trivy k8s --report summary --debug --disable-node-collector --timeout 30m0s
The text was updated successfully, but these errors were encountered:
afdesk
Successfully merging a pull request may close this issue.
Description
Trivy kubernetes scan takes a lot of time for small minikube cluster:
$ time trivy k8s --report summary --debug --disable-node-collector --timeout 30m0s 491,23s user 49,05s system 55% cpu 16:21,43 total
As said in #7661 Trivy fails even for test environment.
Reason
Trivy creates a new scanner for each kubernetes artifact:
trivy/pkg/k8s/scanner/scanner.go
Line 158 in ab3a3b2
trivy/pkg/k8s/scanner/scanner.go
Line 184 in ab3a3b2
Solution
As an idea we can try to optimize using of scanners.
Reproduction Steps
Discussed in #7661
The text was updated successfully, but these errors were encountered: