Skip to content
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

Cloud scanner and sensor agent cant sync and make have double nodes #2049

Open
3 of 6 tasks
gustysap opened this issue Mar 30, 2024 · 0 comments
Open
3 of 6 tasks

Cloud scanner and sensor agent cant sync and make have double nodes #2049

gustysap opened this issue Mar 30, 2024 · 0 comments
Assignees
Labels
bug Something isn't working needs-triage Indicates that issue is not yet triaged and assigned

Comments

@gustysap
Copy link

Describe the bug
I try cloud scanner in GCP and Cloud sensor agent to make monitor vulnerability kubernetes and GCP resources.
But when we use cloud scanner there is capture the nodes generate by GCP API, when we use kubernetes sensor agent the node id and the node name is different

Expected behavior
If the cloud scanner and sensor agent can synchronize then it will be better and the node assets do not need to be duplicated.

Screenshots
List cluster

Components/Services affected

  • UI/Frontend
  • API/Backend
  • Agent
  • Deployment/YAMLs
  • CI/CD Integration
  • Other (specify)
@gustysap gustysap added bug Something isn't working needs-triage Indicates that issue is not yet triaged and assigned labels Mar 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs-triage Indicates that issue is not yet triaged and assigned
Projects
None yet
Development

No branches or pull requests

3 participants