don't add host scanner as excluded ns, use exception instead #1083
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Signed-off-by: YiscahLevySilas1 yiscahls@armosec.io
Overview
Don't exclude "kubescape-host-scanner" namespace. That resulted in cluster-wide resources (like nodes, clusterroles..) being excluded on every scan that uses --enable-host-scan.
Additional Information
We'll be using system exceptions instead.
Important - this PR is blocked by this (PR)[https://github.com/kubescape/regolibrary/pull/301] - adding the exception of host-scanner in regolibrary
Checklist before requesting a review
put an [x] in the box to get it checked
-->