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:
Francois Andrieu 2023-09-12 23:51:43 +02:00
parent 8ebe8332ff
commit e9880dd50e
No known key found for this signature in database

View file

@ -9,7 +9,7 @@ allowPrivilegedContainer: false
allowedCapabilities: null
apiVersion: security.openshift.io/v1
defaultAddCapabilities:
- CAP_SETFCAP
- SETFCAP
fsGroup:
type: RunAsAny
groups: