Details
-
Bug
-
Resolution: Done-Errata
-
Normal
-
4.13, 4.14
-
None
-
Important
-
No
-
Hypershift Sprint 234, Hypershift Sprint 235, Hypershift Sprint 236
-
3
-
False
-
Description
Description of problem:
Cluster does not finish rolling out on a 4.13 management cluster because of pod security constraints.
Version-Release number of selected component (if applicable):
4.14
How reproducible:
Always
Steps to Reproduce:
1.Install 4.14 hypershift operator on a recent 4.13 mgmt cluster 2.Create an AWS PublicAndPrivate hosted cluster on that hypershift cluster
Actual results:
Hosted cluster stalls rollout because the private router never gets created
Expected results:
Hosted cluster comes up successfully
Additional info:
Pod security enforcement is preventing the private router from getting created.
Attachments
Issue Links
- links to
-
RHSA-2023:5006
OpenShift Container Platform 4.14.z security update
- mentioned on
