You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
darnone-sr
changed the title
Neuvector security
Neuvector securityContext
Aug 1, 2023
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.
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.
The text was updated successfully, but these errors were encountered: