Goal

• Easy backup and restore of HostedControlPlanes using OADP

Why is this important?

• This one of the pain points in HCP, having a good UX for the Backup/Restore is key to give the confidence customers deserve.
• Using OADP as a tool for that, we can use an already existent base to work in a smooth integration to support HCP natively using their own plugin

Scenarios

1. As a SRE, I want restore a HCP in the same Management cluster
2. As a developer I want to backup the current status of the HCP in the same Management Cluster
3. As a SRE I want to restore a HCP backup into a different Management cluster

Acceptance Criteria

• Dev
  • Create an OADP plugin which to support HCP backup and restore
  • Integrate the plugin with OADP org as a native one
  • Work with Kubevirt team to use the existent plugin and adapt a new version for HCP
  • Platforms included for this epic:
    • AWS, BM and Kubevirt
    • (OPTIONAL) - Depending on complexity after initial exploration
      • OSP, ARO, ROSA
  • This is focused on Self-Manage but we need to explore it too for ROSA, ARO and OSP platforms.
  • (OPTIONAL) - Migration flow for the plugin.
  • (OPTIONAL) - Work with ACM people to have a good integration with the current DR strategy of the MGMT cluster.
• CI
  • Create E2E jobs to cover Backup/Restore for AWS/Kubevirt/BM.
  • (OPTIONAL) - E2E jobs for HCP migration.
• QE - covered in Polarion test plan and tests implemented
• Release Technical Enablement - Must have TE slides

Dependencies (internal and external)

1. Internal
   1. Create a supported image for the OADP plugin to be built via CI to be stored in quay
2. External
   1. Adapt the image (If necessary) to be integrated as a native plugin in OADP
   2. Integration with MCE for the DR strategy
   3. Integration with Kubevirt provider to support Backup/Restore under HCP

Previous Work (Optional):

1. SRE SOP Migration script: https://github.com/openshift/ops-sop/tree/master/hypershift/utils/dr-script
2. HCP Migrate Agent script: https://github.com/jparrill/hcp-migrate-agent 

Open questions:

1. How the integration should happen with ACM regarding their MGMT Cluster DR?
2. Is migration supported as DR strategy?
3. It needs to have a Konflux pipeline (I think so, but just confirming)?
4. Nodes re-adoption depending of platform?
5. The process to support disconnected environments will need to include the image to different bundles MCE/ACM and OADP?

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Technical Enablement <link to Feature Enablement Presentation>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Enhancement merged: <link to meaningful PR or GitHub Issue>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>