Definition of Done:

• OTA dev can easily launch a cluster with inflight CVO code (hosted control planes) and inflight hypershift code and have access to both of those clusters

Process:

Once per team, get yourself cluster-reader-extended on Hive like this.

And then, per test run:

1. Assemble the pull requests you want to mix together. For example, OTA-854's cvo#926, and the docs-only hypershift#2481 as a stand in for OTA-855.
2. Ask Cluster Bot to launch a 4.14 release with hypershift-hosted, mixing in those pull requests: launch 4.14.0-0.ci,openshift/cluster-version-operator#926,openshift/hypershift#2481 hypershift-hosted
3. Cluster Bot will come back and give you hosted-cluster credentials, if that's all you need.
4. For management-cluster access:
   1. Follow docs to Hive and log in your oc using the usual upper-right Copy login command flow.
   2. Find your Cluster Bot namespace, using the Spyglass run page Cluster Bot links you, like Using namespace https://console-openshift-console.apps.build05.l9oh.p1.openshiftapps.com/k8s/cluster/projects/ci-ln-wg9wcyk.
   3. Watch for a HostedCluster from that namespace: 'oc -n clusters get -o 'jsonpath= {.metadata.name}{"\t"}{.spec.release}{"\n"}' --watch hostedclusters' Alternatively, do a one-off poll, like 'oc -n clusters get -o 'jsonpath={range .items[*]}{.metadata.name}{"\t"}{.spec.release}{"\n"}{end}' hostedclusters | grep ci-ln-wg9wcyk'
   4. Once you have that HostedCluster name, your hosted control plane components will be running in the clusters-$HOSTED_CLUSTER_NAME namespace in the Hive cluster.
   5. If you need hosted-cluster credentials before the install completes and Cluster Bot hands them to you, you can extract them with: oc -n clusters get -o json secret "$HOSTED_CLUSTER_NAME-admin-kubeconfig" | jq -r '.data.kubeconfig | @base64d' >kubeconfig and then export KUBECONFIG=kubeconfig