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

Neuvector securityContext #292

Open
darnone-sr opened this issue Aug 1, 2023 · 1 comment
Open

Neuvector securityContext #292

darnone-sr opened this issue Aug 1, 2023 · 1 comment

Comments

@darnone-sr
Copy link

Neuvector defaults hard coded values for securityContext.privileged. We are actually using another security tool that is identifying that this setting is set to turn in the controller and enforcer. It is advising the value be et to false. We all noticed the chart does not provide securityContext in the values file. Is it necessary that neuvector run as privileged in order to function or can we set this to false? and if so how to we override the securityContext at container level if there is no support for that value in the values file.

@darnone-sr darnone-sr changed the title Neuvector security Neuvector securityContext Aug 1, 2023
@mdnix
Copy link

mdnix commented Nov 5, 2024

I noticed this too.
Is there a specific reason why the pod securityContext and container securityContext can't be configured?
I'd be happy to send a PR with the updated templates to allow such configuration if there's no reason to prevent it.

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

2 participants