add ability to set pod and container security contexts #422
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In order to run Trow in my cluster, I require extra security context options set. Normally, I would just by just using Helm postrendering, but it doesn't seem like postrendering works with Helm Chart Hooks. So I've added a way to set the security contexts.
The webhook deployment seems to typically use the same options as the statefulset, so that's what I've done here. However, with the same security context as the statefulset, the webhook deployment cannot create the data files it wants to in the default data-dir directoy. In my own deployment, I just set the data-dir to
/tmp
, but some decision would have to be made before this can be merged in without breaking the webhook deployment.