charts: add allowPrivilegeEscalation: true to containerSecurityContext to nodeplugin daemonset (backport #2993) #3065
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![mergify[bot]](https://avatars.githubusercontent.com/in/10562?s=60&v=4){kind=small}
When running the kubernetes cluster with one single privileged PodSecurityPolicy which is allowing everything the nodeplugin daemonset can fail to start. To be precise the problem is the defaultAllowPrivilegeEscalation: false configuration in the PSP. Containers of the nodeplugin daemonset won't start when they have privileged: true but no allowPrivilegeEscalation in their container securityContext. Kubernetes will not schedule if this mismatch exists cannot set allowPrivilegeEscalation to false and privileged to true Signed-off-by: Silvan Loser <[email protected]> Signed-off-by: Silvan Loser <[email protected]> (cherry picked from commit 06c4477)
Madhu-1
force-pushed
the
mergify/bp/release-v3.6/pr-2993
branch
from
f72e1d1 to
73567ea
Compare
When running the kubernetes cluster with one single privileged PodSecurityPolicy which is allowing everything the nodeplugin daemonset can fail to start. To be precise the problem is the defaultAllowPrivilegeEscalation: false configuration in the PSP. Containers of the nodeplugin daemonset won't start when they have privileged: true but no allowPrivilegeEscalation in their container securityContext. Kubernetes will not schedule if this mismatch exists cannot set allowPrivilegeEscalation to false and privileged to true: Signed-off-by: Silvan Loser <[email protected]> Signed-off-by: Silvan Loser <[email protected]> (cherry picked from commit f2e0fa2)
Madhu-1
force-pushed
the
mergify/bp/release-v3.6/pr-2993
branch
from
73567ea to
10c8f2e
Compare
Madhu-1
approved these changes
Apr 26, 2022
yati1998
approved these changes
Apr 26, 2022
Madhu-1
added
ci/retry/e2e
|
/retest ci/centos/mini-e2e-helm/k8s-1.22 |
|
@Mergifyio requeue |
❌ This pull request head commit has not been previously disembarked from queue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 is an automatic backport of pull request #2993 done by Mergify.
NOte:- Done manual rebasing