-
Notifications
You must be signed in to change notification settings - Fork 2.5k
feat(k8s): improve artifact selections for specific namespaces #8248
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
Conversation
Really strange this PR has no changes? 🫨 I wonder what happened. |
it's a draft. I prepare test cases at first, and then will update the docs and trivy-kubernetes |
# Conflicts: # go.mod # go.sum
OK, done #8303 |
# Conflicts: # go.mod # go.sum
Co-authored-by: simar7 <[email protected]>
Co-authored-by: simar7 <[email protected]>
@knqyf263 do you mind if we merge this PR? thanks |
@afdesk One comment: isn't it a feature enhancement or bug fix? We might want to update the PR title. It looks like an enhancement to me, but if you don't think so, please feel free to merge this. |
@knqyf263 thanks a lot! you're right! |
…ecurity#8248) Co-authored-by: simar7 <[email protected]>
Description
This PR improves selections of Kubernetes artifacts for users with limited credentials.
Now Trivy can receive resources only for included namespaces.
Before:
Afrer:
Testing
There was added use case here 6e690b9 and tests were broken as expected.
After trivy-kubernetes was update to the latest version 2859ad3, this test case is passed now.
Documentation
there were added parts:


Related issues
Related PRs
Checklist