Custom securityContext in template #392
Merged
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.
Hello, we currently use kubed in a cluster that has very strict security policies enabled. One of them requires us to specify that each k8s workload has to run as non root, not only in the docker image itself, but also in the security context of the workload. Specifically, we need to add the following key:
I have followed the same approach currently used for pod resources, which is converting the values dictionary directly into yaml in the template, using
toYaml
. This would let us modifysecurityContext
to fit our requirement, while the default value is the same as it currently is hardcoded in the template.Please let me know if the pull request is incomplete.