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

Why does the neuvector-scanner run as a deployment rather than a daemonset? #408

Open
cncal opened this issue Jun 17, 2024 · 0 comments
Open

Comments

@cncal
Copy link

cncal commented Jun 17, 2024

As scanner's README says:

The scanner runs with the NeuVector controller to provide registry scan and runtime scan functions.

May I assume that just one scanner running on each node is sufficient? If so, the scanner deployment with default 3 replicas will be bad practice as it's not guaranteed to be evenly distributed among nodes and what do we do when the number of nodes is greater than 3? Yes, Changing the default number of replicas is one way, but I think daemonset would be a better choice.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant