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

Add security context for init container for portal server #212

Conversation

stephen-harris
Copy link

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 the runAsUser 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.]

  • DCO signed
  • Chart Version bumped
  • Variables are documented in the README.md

@stephen-harris stephen-harris force-pushed the feat/add-security-context-for-server-init-container branch from d9f302b to dd70e79 Compare March 10, 2022 10:15
@imrajdas
Copy link
Member

@stephen-harris Have you tested it. I think mongo won't run with these fields in the security context

  runAsUser: 2000
  runAsNonRoot: true

@stephen-harris
Copy link
Author

@rajdas98 Apologies for not replying sooner. Yes I have tested this. The change is for the waitForMongodb container (running a curl image) not the MongoDB container.

@Jasstkn
Copy link
Member

Jasstkn commented Jun 25, 2022

@imrajdas hi. could you take a loot into this PR?

@Jasstkn
Copy link
Member

Jasstkn commented Oct 26, 2022

@imrajdas hi. Can you evaluate if this is still something that we want to have?

@imrajdas
Copy link
Member

@Jasstkn - There is a merge conflict

@Jasstkn
Copy link
Member

Jasstkn commented Nov 25, 2022

@Jasstkn - There is a merge conflict

@imrajdas Hi. I was asking if we want to have this PR opened or it's not up-to-date and we should close it?

@Jasstkn
Copy link
Member

Jasstkn commented Feb 15, 2023

@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?

@Jasstkn
Copy link
Member

Jasstkn commented Aug 29, 2023

No activity in this PR. I'm going to close it in favor of #332

@Jasstkn Jasstkn closed this Aug 29, 2023
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

Successfully merging this pull request may close these issues.

3 participants