-
Story
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
None
-
False
-
-
False
-
None
-
None
-
None
-
None
-
None
Right now, we hardcode the KAS PSA config in the CPO.
This is a constant source of skew vs standalone and PSA tends to get pulled from the release at the last minute, after branch cut, leading to a hypershift fire drill in CI.
We should set the PSA config based on the the OpenShiftPodSecurityAdmission feature gate, that way when it gets disabled in o/api, hypershift doesn't get caught out.
We should also make our e2e conditional on the feature gate