-
Epic
-
Resolution: Unresolved
-
Major
-
None
-
Naming convention configuration for discovered hosted clusters
-
False
-
None
-
False
-
Green
-
To Do
-
ACM-14714 - As a cluster service provider, I want to create, update and delete hosted clusters from a remote hub
-
ACM-14714As a cluster service provider, I want to create, update and delete hosted clusters from a remote hub
-
50% To Do, 50% In Progress, 0% Done
Epic Goal
The goal of this epic is to allow cluster administrator or hosted cluster service provider to be able to configure the ACM hub so that when it discovers and imports hosted clusters from managed MCE clusters, the default discovered managed hosted cluster naming convention, <mce-cluster-name>-<hosted-cluster-name>, can be configured differently.
Why is this important?
There was a customer who wanted ACM to name the discovered hosted cluster to be the same as the hosted cluster name itself because they ensure all hosted clusters are named uniquely in the entire fleet.
Scenarios
...
Acceptance Criteria
...
Dependencies (internal and external)
- ...
Previous Work (Optional):
- ...
Open questions:
- What happens to already discovered and imported hosted clusters?
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.
