-
Spike
-
Resolution: Unresolved
-
Critical
-
None
-
Global Hub 1.6.0
Value Statement
Familiar with the steps for siteconfig. the potential steps can be:
- Create a BM cluster through ACM Hub-A using siteconfig operator v2 and ClusterInstance CR & IBI
- Migrate that BM cluster to Hub-B using the methodology that we have today.
- Then copy over the clusterinstance related resources and edit them to change Hub-A references to Hub-B as outline in the AI generated doc attached (complete-siteconfig-migration.md
doc is the best shot at what we need to do. It may have missed a few steps – and that is why we need to do this test)
- Then try to change the BM cluster through site config operator in Hub-B as explained below.
Definition of Done for Engineering Story Owner (Checklist)
- We will have to manually be able to either -
-
- add a node to the imported cluster through siteconfig operator in Hub-B
- or if we cannot add node (due to hardware constraints), destroy the imported cluster through siteconfig operator in Hub-B
- And note all manual steps that are needed - using the attached doc as a starting point.
- These will have to be programmatically done.
For reference, here is a AI generated sequence flow - installation-flow-diagrams.md