Loading...

XML

Word

Printable

Type: Bug
Resolution: Unresolved
Priority: Critical
Fix Version/s: 4.21.0
Affects Version/s: 4.21
Component/s: apiserver-auth
Labels:
None

Activity Type:
Quality / Stability / Reliability
Blocked:
True
Blocked Reason:

Hide

None

Show
None
Story Points:
None
Severity:
Critical
Regression:
None

Target Backport Versions:
None
Target Version:

4.21.0
Release Blocker:
Approved
Sprint:
None

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

PX Impact Score:

Release Note Status:
In Progress
Release Note Type:
Release Note Not Required
Release Note Text:
None

Escape Reason:
None
Escape Impact:
None
Corrective Measures:
None
SDLC stage when should've been found:
None

Description of problem:

PSA is enabled in 4.21

Version-Release number of selected component (if applicable):

4.21

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-56778 Disable PSA for 4.20

Verified

Assignee:: Kevin Rizza

Reporter:: Krzysztof Ostrowski

Need Info From:: None

Contributors:: None

QA Contact:: Xingxing Xia

Doc Contact:: None

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Created:: 2025/09/12 2:33 PM

Updated:: 2025/09/12 2:34 PM