Epic Goal

As we prepare GA readiness for the hypershift feature, we need to ensure that we can backup and restore:

• the hypershift addon
• the hypershift operator
• the hypershift hosted clusters

and documentation on these. 

This epic should also cover the backup and restore of SD scenario

This epic will mainly be testing and documentation effort.

Why is this important?

...

Scenarios

1. As an ACM cluster admin in self-managed hosted clusters environment, the admin wants to back up all hosted clusters and restore them in another ACM cluster for disaster recovery.
2. As an SRE in ROSA hypershift, the SRE wants to back up all hosted clusters manifestworks and restore them in another service cluster where ACM runs for disaster recovery.

Acceptance Criteria

• Test complete
• How to documentation

Dependencies (internal and external)

1. QE
2. Doc

Previous Work (Optional):

1. ...

Open questions:

1. …

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• 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>

ACM Epic Done Checklist

See presentation and details.

Update with "Y" if Epic meets the requirement, "N" if it does not,  or "N/A" if not applicable.

• _ FIPS Readiness
• _ Works in Disconnected
• _ Global Proxy Support
• _ Installable to Infrastructure Nodes
• _ No impacts to Performance and Scalability
• _ Backup and Restorable