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.

Sign up for GitHub

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

Jump to bottom

Enable specifying serviceAccount and securityContext #421

Closed
mwieczorek opened this issue May 17, 2019 · 2 comments · Fixed by #456
Closed

Enable specifying serviceAccount and securityContext #421

mwieczorek opened this issue May 17, 2019 · 2 comments · Fixed by #456
Labels
enhancement New feature or request good first issue Good for newcomers

Comments

@mwieczorek
Copy link
Contributor

When we create a new Jaeger resource, new serviceAccount with the same name is created and all jaeger components are run with this SA.
It's not possible to set securityContext for the Jaeger components

Enable specifying serviceAccount and securityContext in jaeger CR (top-level and on each component separately).
@jpkrohling jpkrohling added enhancement New feature or request good first issue Good for newcomers labels May 24, 2019
@jpkrohling
Copy link
Contributor

Would you be interested in contributing this feature?

@mwieczorek
Copy link
Contributor Author

I don’t do golang day to day, but I can try.
Of course if someone else from the community finds this „good first issue” and would like to do it - Please comment here and go ahead.

@mwieczorek mwieczorek mentioned this issue Jun 3, 2019
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request good first issue Good for newcomers
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add support for securityContext and serviceAccount
2 participants
@jpkrohling @mwieczorek