Auto-Discovery service in Cluster Internal Central Scans architecture #2437
Replies: 3 comments 1 reply
-
Hi @mguletskii, thanks for submitting this issue. Since, this is rather a question than a bug I convert it to a discussion, so that it'll be picked up easier by others later on. |
Beta Was this translation helpful? Give feedback.
-
Hi, any updates? I think this will be cool feature and allow engineers to get |
Beta Was this translation helpful? Give feedback.
-
Hi, If somebody wan't to pick this up and implement it we are happy to review and merge it but I don't think anybody from the core team has time to work on this right now. |
Beta Was this translation helpful? Give feedback.
-
Hello secureCodeBox team.
First let me say "thank you" for all your work on this project.
We're integrating secureCodeBox solution to our infrastructure and prefer to use Cluster Internal Central Scans architecture (all ScansTypes and Scans stored in one specific namespace).
But Auto-Discovery service trying to create all scans in a service/pod namespace. It's required to have ScanTypes, Hooks and Hooks credentials in every namespace that we want to scan.
How we can use Auto-Discovery service in Cluster Internal Central Scans architecture? Or only way is create all additional entities in every scanning namespaces?
Beta Was this translation helpful? Give feedback.
All reactions