-
Bug
-
Resolution: Done
-
Critical
-
4.13.0
-
None
-
Critical
-
No
-
Hypershift Sprint 235
-
1
-
Approved
-
False
-
Description of problem:
[Hypershift] default KAS PSA config should be consistent with OCP enforce: privileged
Version-Release number of selected component (if applicable):
4.13.0-0.nightly-2023-04-21-084440
How reproducible:
Always
Steps to Reproduce:
1. Install OCP cluster and hypershift operator 2. Create hosted cluster 3. Check the default KAS config of the hosted cluster
Actual results:
The hosted cluster default KAS PSA config enforce is 'restricted' $ jq '.admission.pluginConfig.PodSecurity' < `oc extract cm/kas-config -n clusters-9cb7724d8bdd0c16a113 --confirm` { "location": "", "configuration": { "kind": "PodSecurityConfiguration", "apiVersion": "pod-security.admission.config.k8s.io/v1beta1", "defaults": { "enforce": "restricted", "enforce-version": "latest", "audit": "restricted", "audit-version": "latest", "warn": "restricted", "warn-version": "latest" }, "exemptions": { "usernames": [ "system:serviceaccount:openshift-infra:build-controller" ] } } }
Expected results:
The hosted cluster default KAS PSA config enforce should be 'privileged' in https://github.com/openshift/hypershift/blob/release-4.13/control-plane-operator/controllers/hostedcontrolplane/kas/config.go#L93
Additional info:
References: OCPBUGS-8710
- is blocked by
-
OCPBUGS-12961 [Hypershift] hosted clusters default KAS PSA config should be consistent with OCP
- Closed
- is cloned by
-
OCPBUGS-12961 [Hypershift] hosted clusters default KAS PSA config should be consistent with OCP
- Closed
-
OCPBUGS-20249 Hosted clusters default KAS PSA config should be consistent with OCP
- Closed
- links to