-
Notifications
You must be signed in to change notification settings - Fork 351
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
[jaeger] Add security context to deployment charts in jaeger #37
Conversation
@naseemkullah @pavelnikolov @dvonthenen Can i get a review on this please. |
769ea70
to
863953d
Compare
Please gpg sign all you commits @mehta-ankit |
4fe79ac
to
9091bff
Compare
@naseemkullah I rebased to resolve conflicts and updated the version to 0.19.1. |
9091bff
to
dd512b4
Compare
Sure but we added a new component "ingester" could you add values for it please? |
Signed-off-by: Ankit Mehta <[email protected]>
Signed-off-by: Ankit Mehta <[email protected]>
dd512b4
to
d5cd4b5
Compare
Sure. Added it to the ingester. Should be ready now. |
Great, thanks! |
Signed-off-by: Ankit Mehta [email protected]
When deploying this chart in our cluster we found that we had to add security context to the deployments for them to run as non-root user.
So i created this PR where securityContext is added to the template/charts for deployment and its default value is provided in
values.yaml
file. These can be overwritten if someone uses jaeger chart as a dependency in their own values.yaml file.