-
Bug
-
Resolution: Done
-
Critical
-
4.16
This is a clone of issue OCPBUGS-20249. The following is the description of the original issue:
—
Description of problem:
[Hypershift] default KAS PSA config should be consistent with OCP enforce: privileged
Version-Release number of selected component (if applicable):
Cluster version is 4.14.0-0.nightly-2023-10-08-220853
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
- clones
-
OCPBUGS-30644 Hosted clusters default KAS PSA config should be consistent with OCP
-
- Closed
-
- depends on
-
OCPBUGS-30644 Hosted clusters default KAS PSA config should be consistent with OCP
-
- Closed
-
- is related to
-
OCPBUGS-30644 Hosted clusters default KAS PSA config should be consistent with OCP
-
- Closed
-
- links to
-
RHBA-2024:3327
OpenShift Container Platform 4.15.z bug fix update