coreos-ci: add SETFCAP capability instead of CAP_SETFCAP in SCC
This is to prevent a Pod Security Violation as CAP_SETFCAP is not allowed with the baseline policy (but SETFCAP is).
This commit is contained in:
parent
8ebe8332ff
commit
e9880dd50e
1 changed files with 1 additions and 1 deletions
|
@ -9,7 +9,7 @@ allowPrivilegedContainer: false
|
|||
allowedCapabilities: null
|
||||
apiVersion: security.openshift.io/v1
|
||||
defaultAddCapabilities:
|
||||
- CAP_SETFCAP
|
||||
- SETFCAP
|
||||
fsGroup:
|
||||
type: RunAsAny
|
||||
groups:
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue