-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
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
Add --all-namespaces
flag for trivy k8s
resources scanning
#2901
Labels
kind/feature
Categorizes issue or PR as related to a new feature.
priority/backlog
Higher priority than priority/awaiting-more-evidence.
target/kubernetes
Issues relating to kubernetes cluster scanning
Comments
nilesh-akhade
added
the
kind/feature
Categorizes issue or PR as related to a new feature.
label
Sep 16, 2022
josedonizetti
added
priority/backlog
Higher priority than priority/awaiting-more-evidence.
target/kubernetes
Issues relating to kubernetes cluster scanning
labels
Sep 17, 2022
@chen-keinan What do you think? |
sound reasonable |
This was referenced Apr 20, 2023
When I run configmap with
Trivy Version
Cm Lists
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
kind/feature
Categorizes issue or PR as related to a new feature.
priority/backlog
Higher priority than priority/awaiting-more-evidence.
target/kubernetes
Issues relating to kubernetes cluster scanning
When we do resource scanning, trivy scans it in only the given namespace. This should be improved by adding
--all-namespaces
aka-A
flag.Use cases
cronjobs
andjobs
Possibility to Exclude Jobs/cronjobs from scanning trivy-operator#265Skipping cronjobs, and jobs are particularly useful when the cluster has hundreds non-running jobs; all created from the same spec.
Examples:
The text was updated successfully, but these errors were encountered: