Value Statement

In ACM, we will prevent the creation of the MCH CR if MCE CR already exists and the localClusterName spec field values mismatch between MCH CR and MCE CR

Definition of Done for Engineering Story Owner (Checklist)

• [ ] The MCH webhook successfully validates the presence of a configured local-cluster name in the MCE CR and MCH CR.
• [ ] The MCH webhook correctly handles creation if MCE CR and MCH CR localClusterName are mismatched.
• [ ] The MCH webhook correctly handles creation if MCE CR does not exist (adoption will not occur)
• [ ] Appropriate error messages are generated if validation fails or if the creation criteria are not met.

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](

https://docs.google.com/document/d/1YTqpZRH54Bnn4WJ2nZmjaCoiRtqmrc2w6DdQxe_yLZ8/edit#heading=h.9fvyr2rdriby),

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.