Epic Goal

To explore and evaluate the feasibility of removing the dependency on OLM in MCE, reducing the complexity of deployment and allowing MCE to function independently of OLM-managed installations.

Why is this important?

Removing the OLM dependency in MCE could simplify the installation and upgrade processes, reduce the footprint of the deployment, and offer greater flexibility for users who do not rely on OLM. It also simplifies the operator's architecture, making it easier to manage across diverse environments, especially those that don't require OLM for operator lifecycle management.

Scenarios

• Standalone MCE installation without OLM
• MCE operator upgrade process
• Dependency management and operator updates
• Cross-environment deployment

Acceptance Criteria

• An alternative method (e.g., Helm charts or manual deployment process) for installing and upgrading MCE is documented and validated.

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 - 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.