-
Bug
-
Resolution: Done
-
Critical
-
None
-
4.13.0
-
Critical
-
No
-
Auth - Sprint 233
-
1
-
Approved
-
False
-
Description of problem:
We shouldn't enforce PSa in 4.13, neither by label sync, neither by global cluster config.
Version-Release number of selected component (if applicable):
4.13
How reproducible:
100%
Steps to Reproduce:
As a cluster admin: 1. create two new namespaces/projects: pokus, openshift-pokus 2. as a cluster-admin, attempt to create a privileged pod in both the namespaces from 1.
Actual results:
pod creation is blocked by pod security admission
Expected results:
only a warning about pod violating the namespace pod security level should be emitted
Additional info:
This is currently a noop for 4.14
- blocks
-
OCPBUGS-3985 Allow PSa enforcement in 4.13 by using featuresets
- Closed
- clones
-
OCPBUGS-8709 don't enforce PSa in 4.13
- Closed
- is blocked by
-
OCPBUGS-8709 don't enforce PSa in 4.13
- Closed
-
OCPBUGS-10353 kube-apiserver not receiving or processing shutdown signal after coreos 9.2 bump
- Closed
- is cloned by
-
OCPBUGS-16726 [4.14] don't enforce PSa in 4.14
- Closed
- is related to
-
AUTH-351 Impact don't enforce PSa in 4.13
- Closed
- is triggered by
-
OCPBUGS-3663 don't enforce PSa in 4.12
- Closed
- relates to
-
JBEAP-24518 Operator isn't compatible with new security standards in upcoming OCP
- Closed
- links to