Cluster deployment on OpenShift virtualization consistently fails to reach a "Ready" state, getting stuck in "Partial" with initial degraded/missing components and an inaccessible kube-apiserver via kubeadmin.

OpenShift 4.18.10 (as indicated by oc get co output)

100% - consistently reproducible with every new hosted cluster creation.

Create a new hosted cluster on OpenShift virtualization using the ACM dashboard.
Define the necessary hostedcluster and nodepool resources.
Monitor the cluster's progress and status. 

The hosted cluster status remains "Partial" instead of "Ready".
Initially, the kube-scheduler deployment is in a degraded state.
The ignition server deployment is not found.
Many conditions are not found in the CVO.
The kube-apiserver of the hosted cluster cannot be accessed directly using the kubeadmin user (Login failed 401 Unauthorized).
Manual intervention is required to approve pending CSRs after retrieving the kubeconfig from the admin-kubeconfig secret, which allows access via oc commands but does not resolve the kubeadmin login issue or full cluster readiness. 

The hosted cluster should reach a "Ready" state after creation.
All cluster components should be healthy and fully deployed without manual intervention.
The kube-apiserver should be accessible via the kubeadmin user immediately after deployment.
No manual approval of CSRs or restarting of pods should be required for a successful deployment. 

Must-gather for failing cluster "hosted-418" has been attached.
The issue is observed across all newly created hosted clusters, indicating a systemic problem rather than an isolated incident.
oc get co output shows all cluster operators as True for AVAILABLE and False for PROGRESSING and DEGRADED, despite the cluster's overall "Partial" status and kubeadmin login failure.