Epic Goal

• Understand the expected MCE use case for SiteControl with ZTP, Assisted and as a template.

  Why is this important?

• Simplify templating of clusters, this has been an ask for quite some time from Product Management

  Scenarios

• SiteConfig provides a re-usable provisioning template for Classic and HCP?? cluster types

  Acceptance Criteria

1. ACM use cases are well defined
2. Built via Konflux
3. Product Management has signed off
4. Release pattern is defined (outside MCE core)
5. Doc is notified/aware
6. Threat model is created
7. QE is notified/aware

Dependencies (internal and external)

1. MCE installer
2. Konflux
3. PM
4. Doc
5. Threat Model (security)
6. QE

Previous Work (Optional):

1. SiteControl v1 build out

Open questions:

1. Review of the code that will be used to build the Site Control Image
2. Rename the SiteControl CRD in MCE/ACM

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.