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 wait-for-mongodb #332

Merged

Conversation

Calvinaud
Copy link
Contributor

  • Add securityContext in values.yaml
  • Using this securityContext in auth-server-deployment.yaml and server-deployment.yaml
  • Bumping Chart version to 2.16.0 (I hesitate between bumping to 2.16.0 or 2.15.12 cause not sure if this change can be considered a bug fix)
  • Regenerating docs with helm-docs

What this PR does / why we need it:

Which issue this PR fixes

(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

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

- Add securityContext in values.yaml
- Using this securityContext in auth-server-deployment.yaml and server-deployment.yaml
- Bumping Chart version to 2.16.0
- Regenerating docs with helm-docs

Signed-off-by: Calvin Audier <[email protected]>
@Calvinaud
Copy link
Contributor Author

I was not sure if this change needed to be considered as a bug fix (and bump to 2.15.11) or a added feature (and bump to 2.16.0). I can change if needed.

@Calvinaud
Copy link
Contributor Author

Didn't see the PR, #212. Should I close this one in favor of the previous one ?

@Jasstkn
Copy link
Member

Jasstkn commented Aug 29, 2023

Let me take a look. Will reply by EOD, thanks!

charts/litmus/Chart.yaml Show resolved Hide resolved
charts/litmus/values.yaml Outdated Show resolved Hide resolved
@Jasstkn
Copy link
Member

Jasstkn commented Aug 29, 2023

Let me take a look. Will reply by EOD, thanks!

Mentioned PR wasn't updated on requested, closed it in favor of yours. Please, let me know if you have any questions about the comments that I've left.

- Update values.yaml to remove default values for security securityContext
- Example values for securityContext as comments
- Regenerating docs with helm-docs
- Switching for bump to 2.16.0 to bump to 2.15.11

Signed-off-by: Calvin Audier <[email protected]>
@Calvinaud Calvinaud requested a review from Jasstkn August 30, 2023 08:39
Copy link
Member

@Jasstkn Jasstkn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 🚀 Thank you for your contribution!

@imrajdas @ispeakc0de can you take a look here?

@Jasstkn Jasstkn merged commit 83daecc into litmuschaos:master Aug 31, 2023
10 checks passed
@Jasstkn
Copy link
Member

Jasstkn commented Aug 31, 2023

@Calvinaud gonna be released in a few moments!

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.

Cannot deploy litmus chaoscenter cause of missing securityContext
3 participants