Epic Goal

To ensure that the OpenShift OADP is compatible with and functions effectively on the HyperShift form factor of OpenShift, providing a seamless backup / restore experience for applications in HyperShift hosted clusters.

Why is this important?

As the HyperShift form factor of OpenShift gains popularity for its cost-effectiveness, portability, and separation of management and workloads, it is crucial to ensure that the OADP can fully support and facilitate application migrations within HyperShift hosted OpenShift clusters. This compatibility will enable organizations to backup and restore their applications to HyperShift seamlessly, taking advantage of its benefits while leveraging the tools and resources provided by OADP.

Acceptance Criteria (Mandatory)

• OADP is compatible with the technical architecture and components of the HyperShift form factor of OpenShift (Hosted Control Planes).
• OADP can be successfully deployed and configured on HyperShift hosted OpenShift clusters, ensuring seamless integration with the HyperShift environment.
• OADP provides comprehensive support for the migration process within HyperShift hosted clusters, including tools, documentation, and best practices specific to HyperShift.
• Performance and scalability tests demonstrate that OADP performs optimally within the HyperShift environment, enabling efficient migration of Containers at scale.

Development work:

• OADP on OpenShift HCP is being used by customers today, no additional work required outside of Doc and QE.

QE Acceptance Criteria

• Dev testing or Dev CI is not a prerequisite 

TESTING
https://issues.redhat.com/browse/CNTRLPLANE-316 in the epic I have 3 scenarios # As a SRE, I want restore a HCP in the same Management cluster

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