Silvan Loser b50d8596ea deploy: allowPrivilegeEscalation: true in containerSecurityContext ... 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 <silvan.loser@hotmail.ch> Signed-off-by: Silvan Loser <33911078+losil@users.noreply.github.com> (cherry picked from commit f2e0fa28fb)		2022-04-26 10:02:04 +00:00
..
cephcsi/image	build: remove cache while building container image	2022-03-28 06:09:27 +00:00
cephfs/kubernetes	deploy: allowPrivilegeEscalation: true in containerSecurityContext	2022-04-26 10:02:04 +00:00
nfs/kubernetes	deploy: add deployment artifacts for NFS support	2022-04-01 10:37:41 +00:00
rbd/kubernetes	deploy: allowPrivilegeEscalation: true in containerSecurityContext	2022-04-26 10:02:04 +00:00
Makefile	deploy: add deployment artifacts for NFS support	2022-04-01 10:37:41 +00:00
scc.yaml	nfs: add provisioner & plugin sa to scc.yaml	2022-04-13 13:23:48 +00:00