Epic Goal

To drive the initial configuration of the code and CI of the MMO.

Why is this important?

So that further development can be expedited and guidelines/standards of coding are shared across the team through pre-submit tests in the CI.

Scenarios
1. …

Acceptance Criteria

• We have static tests running in CI for the MMO repo
• The MMO can be deployed via OLM (even manually with a custom build catalog)
• Manifests (RBAC-related in particular) are reviewed

Dependencies (internal and external)
1. …

Previous Work (Optional):
1. The repository started as a POC to drive the writings of https://github.com/openshift/enhancements/pull/1417.

Open questions::
1. …

Done Checklist

CI - For new features (non-enablement), existing Multi-Arch CI jobs are not broken by the Epic
Release Enablement: <link to Feature Enablement Presentation>
DEV - Upstream code and tests merged: <link to meaningful PR orf GitHub Issue>
DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
DEV - If the Epic is adding a new stream, downstream build attached to advisory: <link to errata>
QE - Test plans in Test Plan tracking software (e.g. Polarion, RQM, etc.): <link or reference to the Test Plan>
QE - Automated tests merged: <link or reference to automated tests>
QE - QE to verify documentation when testing
DOC - Downstream documentation merged: <link to meaningful PR>
All the stories, tasks, sub-tasks and bugs that belong to this epic need to have been completed and indicated by a status of 'Done'.