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

Supply runAsUser at the container level #1240

Merged
merged 1 commit into from
Apr 19, 2019
Merged

Conversation

tmc
Copy link
Contributor

@tmc tmc commented Apr 17, 2019

Without this the istio-init initContainer fails.

This is a similar issue as existed in this chart: helm/charts@4daf2d0

@consideRatio
Copy link
Member

Thanks! It was great that you provided an example of another repo that did the same thing as well!

It is my understanding that this change would simply shift the requested security context to be container-scoped rather than pod-scoped. In other words, to narrow down the scope rather than broaden it. That should be perfectly fine!

LGTM!

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.

2 participants