-
Bug
-
Resolution: Done-Errata
-
Critical
-
4.16.0, 4.17.0
-
Critical
-
No
-
Hypershift Sprint 255
-
1
-
Approved
-
False
-
-
N/A
-
Release Note Not Required
-
Done
Clone of original bug to ensure the change is made in HyperShift
Description of problem:
We shouldn't enforce PSa in 4.16, neither by label sync, neither by global cluster config.
Version-Release number of selected component (if applicable):
4.16
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:
- blocks
-
OCPBUGS-35369 [4.16][HyperShift] don't enforce PSa in 4.16
- Closed
- clones
-
OCPBUGS-26466 [4.16] don't enforce PSa in 4.16
- Closed
- is cloned by
-
OCPBUGS-35369 [4.16][HyperShift] don't enforce PSa in 4.16
- Closed
- is related to
-
OCPBUGS-34881 [4.17] maybe enforce PSA in 4.17
- Closed
- links to
-
RHEA-2024:3718 OpenShift Container Platform 4.17.z bug fix update
(2 links to)