-
Spike
-
Resolution: Done
-
Major
-
None
-
None
Value Statement
Several options for how to move forward have presented themselves. The PMs need to be involved to nail down how these issues will be handled:
- Should renaming local-cluster be allowed post-install?
- What should happen if ACM adopts MCE and the localClusterName spec field is mismatched?
Summary
- When MCE is installed Standalone: the user can rename local-cluster with the MCE CR with localClusterName
- When ACM is installed on a clean cluster (not adopting MCE): the user can rename local-cluster in the MCH CR with localClusterName
- When ACM is installed and adopting a pre-existing MCE: The MCH CR and MCE CR spec fields localClusterName must match or ACM installation will be blocked. User is responsible for resolving the issue before continuing by changing either one of the two CRs
Slack threads involved:
- https://redhat-internal.slack.com/archives/CSZLD3RSM/p1744651256199289
- https://redhat-internal.slack.com/archives/GUGT7F0NS/p1744314242357659
Discussion Document: https://docs.google.com/document/d/1gda2KJTjterhWu8Mw7q3J7esawvvMXLQ7JbZX4PxyA4/edit?usp=sharing
Meeting recording for context: https://drive.google.com/file/d/12nK2QHW33YluX_E9tc-clseThfpvFuAH/view?usp=sharing