-
Story
-
Resolution: Unresolved
-
Major
-
None
-
2
-
False
-
None
-
False
-
-
ACM-14714 - As a cluster service provider, I want to create, update and delete hosted clusters from a remote hub
-
-
-
2
-
Workload Mgmt Train 21 - 1, Workload Mgmt Train 21 - 2
-
None
Value Statement
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. (No prefix)
Some might want to use a prefix other than the MCE managed cluster name.
Definition of Done for Engineering Story Owner (Checklist)
- This story will implement the discovered cluster name prefix.
Development Complete
- The code is complete.
- Functionality is working.
- Any required downstream Docker file changes are made.
Tests Automated
- [ ] Unit/function tests have been automated and incorporated into the
build. - [ ] 100% automated unit/function test coverage for new or changed APIs.
Secure Design
- [ ] Security has been assessed and incorporated into your threat model.
Multidisciplinary Teams Readiness
- [ ] Create an informative documentation issue using the Customer
Portal Doc template that you can access from [The Playbook](
and ensure doc acceptance criteria is met.
- Call out this sentence as it's own action:
- [ ] Link the development issue to the doc issue.
Support Readiness
- [ ] The must-gather script has been updated.
- is documented by
-
ACM-15775 Implement a configuration for discovered hosted cluster naming convention
- Backlog