Feature Overview

Leverage the NextGen Control Plane in ROSA & ARO deployments
Include the following:

• Base foundation for cluster registration
• HyperShift Addon for HostedCluster registration (but probably not install of the HyperShift Operator)
• Config Policy capabilities
• Backup and Restore

Goals

• Create a lite control plane that host 1k-3k clusters (deployment must be small
• Highly available and able to restore quickly
• Able to re-acquire managed infrastructure if resources are recreated (from backup or from orchestrator, like Cluster Service )

Requirements

This Section: A list of specific needs or objectives that a Feature must
deliver to satisfy the Feature.. Some requirements will be flagged as MVP.
If an MVP gets shifted, the feature shifts. If a non MVP requirement slips,
it does not shift the feature.

Requirement

• Must run on xKS
• Create the smallest possible control plane to handle 1000-2000 Hosted Clusters
• Continue to include the Hosting Cluster / Management Cluster with the HyperShift Addon
• Backup the Managed Cluster data so that the pod can be replaced (including the PVC) and restored in < 10min
• Allow the CP (Control Plane) to be able to start with a copy of the PVC
• Backup the required 1000-2000 Managed clusters every 1hr or after a NEW ManagedCluster is created, how fast can this be?
• Define how the API needs to be defined so a NEW instance of the pod can be started in the following scenarios:
  1. Start a new instance on the same cluster
  2. Start a new instance on a different cluster with the same data (migration or restore)

(Optional) Use Cases

This Section:

• Main success scenarios - high-level user stories
• Alternate flow/scenarios - high-level user stories
• Deploys and is highly available with 1k Managed Hosted Clusters

Questions to answer

• How fast can we backup and restore with 1k, 2k, 3k clusters
• How large is the CP deployment with 1k, 2k, 3k clusters

Out of Scope

• …

Background, and strategic fit

This Section: What does the person writing code, testing, documenting
need to know? What context can be provided to frame this feature?

Assumptions

• ...

Customer Considerations

• ...

Documentation Considerations

Questions to be addressed:

• What educational or reference material (docs) is required to support this
  product feature? For users/admins? Other functions (security officers, etc)?
• Does this feature have a doc impact?
• New Content, Updates to existing content, Release Note, or No Doc Impact
• If unsure and no Technical Writer is available, please contact Content
  Strategy.
• What concepts do customers need to understand to be successful in
  [action]?
• How do we expect customers will use the feature? For what purpose(s)?
• What reference material might a customer want/need to complete [action]?
• Is there source material that can be used as reference for the Technical
  Writer in writing the content? If yes, please link if available.
• What is the doc impact (New Content, Updates to existing content, or
  Release Note)?