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.
added support to explicitly define the
fsGroup
according to https://kubernetes.io/docs/reference/kubernetes-api/workload-resources/pod-v1/#security-contextI know that in theory it could be overwritten in yaml declaration but there seems to be an xor with limit definitions. explicitly setting it works
Testing done
For testing i created a jenkins job with the following spec:
and checked if the securityContext of the resulting pod is set to the expected fsGroup:
which was set as expected
Submitter checklist