feat(trait): enforce Pod and Container security context #5461
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.
This PR introduce a default value for both Pod and Container Security Context in order to strengthen the security on the cluster and avoid possible privilege escalations. Note that we still must set
runAsNonRoot
value asfalse
by default as we are building container to run withroot
user. We will work on a follow up issue to remove such a constraint and set this default astrue
when we are ready.The resulting Pod executed (whichever is the controller strategy) will be like the following:
The default configuration is enriched automatically in Openshift cluster which are already enforcing these policies with the addition of a default
runAsUser
value.Release Note