-
Notifications
You must be signed in to change notification settings - Fork 327
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
[SECURITY] sidecar security context config #347
Comments
Hi, is this specifically for the injected sidecars when using service mesh? |
Hey @lkysow, yeah that is exactly it |
I have Consul Connect version |
I've updated the container securitycontexts and actually got this working. I'll rework it so that it is configurable via helm and has a default, then submit a PR |
Sorry I havn't forgotten. Hopefully get around to the PR this side of Christmas |
Closing as this is addressed via #493 |
Containers in my Kubenernetes environment must not run as root and need
runAsUser
set for the security context.e.g
securityContext: runAsUser: 1000
Is this possible? Can it be made possible?
The text was updated successfully, but these errors were encountered: