-
Story
-
Resolution: Done
-
Major
-
ACM 2.14.0
-
Product / Portfolio Work
-
3
-
False
-
-
False
-
-
-
-
Installer Sprint 2025-59
-
None
Value Statement
In ACM, customers want the ability to specify the local-cluster name instead of relying on the hardcoded "local-cluster" value. This will help avoid confusion in a global hub setup where multiple regional hubs may share the same name, and ensure proper validation of the local-cluster through the local-cluster=true label.
Definition of Done for Engineering Story Owner (Checklist)
- [ ] The hard-coded reference to the local-cluster ManagedCluster name has been removed.
- [ ] MCE now uses the specified local-cluster name when creating the local-cluster resource.
- [ ] MCH inherits the local-cluster name is adopting MCE standalone instance.
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 cloned by
-
ACM-18700 MCH: Ensure that the MCH webhook validates deletion only if the local-cluster is correctly labeled and named
-
- Closed
-