Epic Goal

• Make it easier to install SubmarinerAddon by allowing the user to configure it through the MCH at ACM install time.

Why is this important?

• To ensure that we simplifying the installation process of ACM, OLM will only deploy MCH. SubmarinerAddon will act as a sub-component that will be deployed and managed by MCH.

Scenarios

1. Customer wishes to deploy ACM without SubmarinerAddon deployed by default.
2. Customer wishes to deploy ACM with SubmarinerAddon deployed by default.

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• ...

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. ...

Open questions:

1. …

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 - Downstream documentation merged: <link to meaningful PR>