-
Bug
-
Resolution: Unresolved
-
Critical
-
4.20
-
None
-
Quality / Stability / Reliability
-
True
-
-
None
-
Critical
-
None
-
None
-
Approved
-
None
-
In Progress
-
Release Note Not Required
-
None
-
None
-
None
-
None
-
None
Description of problem:
PSA is enabled in 4.20
Version-Release number of selected component (if applicable):
4.20
How reproducible:
Always
Steps to Reproduce:
1. Create a namespace in both OCP and HCP clusters 2. Check global pod-security.kubernetes.io/enforce config for both OCP and HCP clusters
Actual results:
Namespace and global configs of pod-security.kubernetes.io/enforce are set for both OCP and HCP clusters.
Expected results:
Should not be set for either OCP or HCP clusters.
Additional info:
We need to disable the feature flag.
- clones
-
OCPBUGS-56773 Disable PSA for 4.19
-
- Closed
-
- is cloned by
-
OCPBUGS-61678 Disable PSA for placeholder for next release
-
- New
-
- is depended on by
-
OCPBUGS-56773 Disable PSA for 4.19
-
- Closed
-
-
OCPBUGS-56777 Don't enforce restricted PSA for 4.19 hosted cluster
-
- Closed
-
- links to
(1 links to)