-
Bug
-
Resolution: Unresolved
-
Critical
-
None
-
4.18
-
Critical
-
No
-
Approved
-
False
-
-
Release Note Not Required
-
In Progress
This is a clone of issue OCPBUGS-26466 but the description is modified for 4.18.
—
Description of problem:
We shouldn't enforce PSa in 4.18, neither by label sync, neither by global cluster config.
Version-Release number of selected component (if applicable):
4.18
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:
- clones
-
OCPBUGS-26466 [4.16] don't enforce PSa in 4.16
- Closed
- depends on
-
OCPBUGS-45916 [4.19] Maybe enforce PSa
- Closed
- is depended on by
-
OCPBUGS-45600 HyperShift should enforce privileged PSA by default in 4.18
- New
- is triggering
-
OCPBUGS-45600 HyperShift should enforce privileged PSA by default in 4.18
- New
- links to