-
Epic
-
Resolution: Done
-
Normal
-
None
-
Investigate support for an ACM standby via one of the ManagedClusters
-
False
-
None
-
False
-
Not Selected
-
To Do
Epic Goal
Can a two node scenario sustain the restore of an ACM to one of it's Managed Clusters.
Since by default local-cluster is enabled, how does that affect a restore on a cluster that used to be Managed Cluster.
Why is this important?
Two rack scenarios
Scenarios
1. ACM on hub 1 on Rack 1 fails. Can you restore ACM to hub 2 on Rack 2 that was managed by ACM?
2. Needs to support Ramen DR recovery flows
Acceptance Criteria
Either this can or can not be supported.
Dependencies (internal and external)
- Agent support when restoring.
- Use local-cluster vs remote
- Could use hosted mode
- restore with local-cluster agent on a cluster where the managed cluster agent is already installed
Previous Work (Optional):
- local-cluster rename
- Hosted Mode
- Agent namespace change
- Backup and restore
Open questions:
- Can we set local managed FALSE, then import the cluster with its regular name
- Should we use rename local cluster
- Can you restore on a Managed Cluster
Done Checklist
- Release Enablement <link to Feature Enablement Presentation>
- DEV -Process to move ACM between two nodes that it manages is complete.
- QE - Validated
- DOC - Doc for product or just for ODF
- duplicates
-
ACM-14960 ACM restore onto one of it's managed clusters. 2x Cluster scenario or 2+N
- New