-
Epic
-
Resolution: Obsolete
-
Critical
-
None
-
None
-
Multiple hub architecture for a managed cluster (Observability)
-
False
-
False
-
To Do
Epic Goal
- Allow a cluster to be managed by multiple hub clusters
Why is this important?
We may have use cases where different entities will want to leverage Open Cluster Management technology on the same clusters. For example below: a Red Hat SRE team may want to adopt multicluster engine to help manage their fleet of ROSA, OSD, ARO, ROKS clusters. The customer of those clusters may also want to purchase RHACM and import those clusters to use App, GRC, Observability, etc features.
- …
Scenarios
- ...
Acceptance Criteria
- CI - MUST be running successfully with tests automated
- Release Technical Enablement - Provide necessary release enablement details and documents.
- ...
Dependencies (internal and external)
- ...
Previous Work (Optional):
- …
Open questions::
- …
Done Checklist
- CI - CI is running, tests are automated and merged.
- Release Enablement <link to Feature Enablement Presentation>
- DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
- DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
- DEV - Downstream build attached to advisory: <link to errata>
- QE - Test plans in Polarion: <link or reference to Polarion>
- QE - Automated tests merged: <link or reference to automated tests>
- DOC - Downstream documentation merged: <link to meaningful PR>
