Verify MCE and HyperShift from PRE-10. All pods Running, CLI works.
Additionally: check pod capacity on the SNO node BEFORE creating a Hosted Cluster (default is max 250 pods per node) — a single Hosted Cluster requires approximately 30–40 additional pods for the control plane, independent of free CPU/RAM. If the node is already near the pod limit (e.g. due to many leftover test VMs/deployments from previous test cases), creation fails with 'Too many pods' even though CPU/RAM would be available.
Prerequisites checklist
Confirm these before running steps:
1oc get mce
→ Status: Available
2oc get pods -n hypershift
→ hypershift-operator: Running
3hcp version
→ Client/Server version must match
4oc get hostedcluster -A
→ no error (empty is OK)
oc describe $(oc get nodes -o name) | grep -A3 'Non-terminated Pods'→ shows e.g. 'Non-terminated Pods: (187 in total)' and the capacity limit
oc get node -o jsonpath='{.items[0].status.allocatable.pods}{"\n"}'→ maximum pod count for this node (default usually 250)
Rule of thumb: plan for at least 50 free pod slots for a Hosted Cluster (30–40 control-plane pods + worker VM pods + buffer)
If little buffer remains: clean up test VMs/deployments no longer needed from previous test cases (see respective 'Cleanup' steps)
5If the maximum pod count per node is 250 and you plan to use a single-node cluster, you will most likely need to increase the limit. Create a KubeletConfig with maxPods set to 500 (full block in the Commands / YAML tab)
ATTENTION: This will REBOOT the node!
6One-time: allow wildcard routes on the management cluster — required later for console access to Hosted Clusters (TC-HCP-002); best done now
oc patch ingresscontroller -n openshift-ingress-operator default --type=json -p '[{"op":"add","path":"/spec/routeAdmission","value":{"wildcardPolicy":"WildcardsAllowed"}}]'