-
Epic
-
Resolution: Done
-
Critical
-
Global Hub 1.3.0
-
Allow managed hub clusters have local-cluster enabled
-
False
-
None
-
False
-
Green
-
To Do
-
0% To Do, 0% In Progress, 100% Done
-
GH Train-16 1, GH Train-16 2, GH Train-17 1, GH Train-17 2, GH Train-18 1, GH Train-18 2, GH Train-19 1, GH Train-19 2
Epic Goal
This epic goal is to remove the requirement that disable the local-cluster in ACM hub cluster before importing as a managed hub cluster of the global hub.
Why is this important?
1. Disable the hub self management has an impact on the local policy and policy automation in their existing ACM hub cluster.
Scenarios
1. We can import ACM hub cluster with local-cluster enabled in global hub
Acceptance Criteria
...
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 - Doc issue opened with a completed template. Separate doc issue
opened for any deprecation, removal, or any current known
issue/troubleshooting removal from the doc, if applicable.
