Forbid container privilege escalations #960
Open
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.
How to categorize this PR?
/area security
/area compliance
/kind enhancement
/platform gcp
What this PR does / why we need it:
This PR sets the
securityContext.allowPrivilegeEscalation
field tofalse
for every container, which does not havesecurityContext.Privileged
set totrue
or one ofCAP_SYS_ADMIN/SYS_ADMIN
capabilities added.Which issue(s) this PR fixes:
Part of gardener/gardener#11139
Special notes for your reviewer:
cc @AleksandarSavchev
Release note: