-
Notifications
You must be signed in to change notification settings - Fork 88
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
Add security context for init container for portal server #212
Add security context for init container for portal server #212
Conversation
Signed-off-by: Stephen Harris <[email protected]>
d9f302b
to
dd70e79
Compare
@stephen-harris Have you tested it. I think mongo won't run with these fields in the security context
|
@rajdas98 Apologies for not replying sooner. Yes I have tested this. The change is for the |
@imrajdas hi. could you take a loot into this PR? |
@imrajdas hi. Can you evaluate if this is still something that we want to have? |
@Jasstkn - There is a merge conflict |
…container Signed-off-by: Maria Kotlyarevskaya <[email protected]>
@stephen-harris hi! do you want to continue working on this? I think that it's enough to make security context configurable. then users can decide if they want to configure it or not? |
No activity in this PR. I'm going to close it in favor of #332 |
What this PR does / why we need it:
Add's support for configuring the securityContext of the litmus-server init container. In environments where runAsNonRoot is automatically set to
true
the init container fails to start because therunAsUser
is not specified.This also aligns the configuration of the init container with the other containers in this deployment.
Which issue this PR fixes
n/a
Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]