User Story:

As a OpenShift deployer, I want to be able to

• have access to assisted-service and its data after the ephemeral node reboots and becomes a member of cluster 0

so that I can

• have the node running assisted-service become a member of cluster 0
• have access to installation logs and artifacts for cluster0 after the node running the ephemeral assisted-service reboots and pivots to become a member of cluster 0
• use the assisted-service UI on cluster 0
• minimize the number of nodes required to deploy the OpenShift cluster

In the compact cluster case, there are two options being explored on how to deploy the initial assisted-service. The first option deploys assisted-service on top of the bootstrap node (ephemeral node) using its OpenShift API. Here we need to copy the database data and the CRs from the bootstrap to cluster 0 before assisted-service starts on cluster 0.

The second option is where we do not have the OpenShift API available on the bootstrap node when deploying the initial assisted-service. Here we still need to copy the database data, but the CRs will need to be recreated on cluster 0 so that it matches what is in the database before the assisted-service controllers are started on cluster 0.

Acceptance Criteria:

Description of criteria:

• cluster 0 deploys assisted-service using the infrastructure operator or multi-cluster-operator
• database data from the ephemeral assisted-service is copied over to the cluster 0
• CRs from the ephemeral assisted-service is also copied over to the cluster 0
• both sets of data are copied over to cluster 0 before the cluster 0 assisted-service starts up
• the ephemeral node waits for assisted-service to finish copying its data into cluster 0 before rebooting
• clients of the ephemeral assisted-service are switched over to using the cluster 0 assisted-service when the ephemeral node reboots

(optional) Out of Scope:

Detail about what is specifically not being delivered in the story

Engineering Details:

• (optional) https://github/com/link.to.enhancement/
• (optional) https://issues.redhat.com/link.to.spike
• Engineering detail 1
• Engineering detail 2

This requires/does not require a design proposal.
This requires/does not require a feature gate.