Epic Goal

To help guarantee turnkey integrations between ACM and ODF, this epic proposes that we enable a component flag to enable MCO.  Need to use the ODF acronym in the flag.

We will also be looking to include a static Infrastructure > Storage page in the console.

Why is this important?

Lower the bar of entry to leveraging MCO

Scenarios

1. Day 1 I want to install ACM with MCO (declaratively)
2. Day 2 I want to enable MCO for an ACM install  (declaratively)
3. Day 2 I want to discover MCO, from the console and be able to activate it with minimal time investment.

Acceptance Criteria

odf_managed-cluster-orchestrator flag, that is "false" by default in MCH

Dependencies (internal and external)

1. MCO version is supplied to ACM for the MCH operator before release

Previous Work (Optional):

1. MCO operator is published

Open questions:

1. Do we need to support different versions(channel) of MCO from a given MCH?
   1. Is MCO version dependent on ACM, OCP or both?

Done Checklist

• CI - Install has feature
• 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 - Validate feature flag works in false/true position
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Reference to ODF - Managed Clsuter orchestration documentaiton