-
Outcome
-
Resolution: Done
-
Critical
-
None
-
None
-
Theme
-
L
-
False
-
Outcome Overview
This outcome aims to enable the migration or movement of control-planes between management clusters for self-managed Hosted Control Plane deployments. The key objective is to ensure system robustness and flexibility in scenarios such as failure recovery, maintenance, region change, cost reductions and more.
Successfully implementing this feature will align with our strategic goals of increasing system resilience, enhancing user satisfaction by reducing potential downtime, and providing greater operational flexibility.
Approach
Today we don't have a standard component that can auto-migrate control-planes between management clusters. This process usually housed in shell scripts. We should explore standardizing the process and potentially using pre-existing components that have fleet visibility (e.g., ACM).
Success Criteria
Success for this strategic outcome will be determined by the following criteria:
- Ability to migrate control-planes seamlessly between management clusters in response to failures, maintenance requirements, or region changes.
- Minimization of downtime and disruption during control-plane migration.
- Positive feedback from users indicating ease of migration and increased confidence in system reliability.
- Documentation of clear procedures and guidelines for control-plane migration.
- is related to
-
HOSTEDCP-1485 [SPIKE] PoC over Backup/Restore a HostedCluster using ACM/MCE vol-sync
- To Do
- relates to
-
OCPSTRAT-1088 Deeply Integrate Hosted Control Planes into ACM
- New
-
OCPSTRAT-1083 [Spike] Enable Transitioning from Standalone OpenShift to Hosted Control Planes
- New