-
Epic
-
Resolution: Done
-
Critical
-
None
-
None
-
Global Hub to manage the lifecycle of local hub clusters
-
False
-
None
-
False
-
To Do
OCP/Telco Definition of Done
Epic Template descriptions and documentation.
<--- Cut-n-Paste the entire contents of this description into your new Epic --->
Epic Goal
- The customers can install the global hub from operatorhub to the existing ACM hub cluster.
- When the customers install the global hub from operatorhub, the existing managed clusters can be able to install as a regional hub cluster.
- When the customers install the global hub from operatorhub, the existing policies and apps can be switched to the global resources.
Why is this important?
- The customers do not want to have a new cluster for global hub. They choose the existing ACM cluster to be a global hub cluster
Scenarios
- There are many ACM hub clusters in the customers' environment. They decide to use global hub cluster to manage the ACM hub clusters. They want to install global hub in one of the existing ACM hub clusters.
-
- The customers can install global hub cluster from operatorhub.
- The existing manged clusters of ACM hub 2 will be installed as regional hub clusters. The customers can add a label global-hub.open-cluster-management.io/regional-hub-type=NoHubAgentInstall to the managed cluster to tell global hub that this managed cluster won't be managed by global hub.
- Only support install ACM with the same verions of the global hub
- Do not support upgrade ACM in the regional hub cluster
- The customers can manually import ACM hub 1 and ACM hub 3 as a regional hub clusters of global hub cluster.
- Uninstall global hub in ACM hub 2 won't uninstall the ACM in the regional hub cluster
- Cannot delete MGH CR if there are the regional hub clusters and report the reason in MGH CR status
- Upgrade the global hub together with the regional hub clusters (Upgrade is not in scope)
-
- Only support install ACM with the same versions of the global hub
- Do not support upgrade ACM in the regional hub cluster separately
- Support automatically upgrade the global hub version and regional hub version by leverage the olm capability . e.g.: 2.7.0 -> 2.7.1
- Support manually upgrade the global hub version and regional hub version together. e.g.: 2.7.x -> 2.8.0
Acceptance Criteria
- Able to see ACM hubs health data in the Global Hub
- Able to upgrade the entire suite of clusters (Global Hub and all ACM hubs [and implicitly managed clusters]) to ACM a.b
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>
