Epic Goal

• Ship OBO in the redhat-operators catalog
  • This Epic tracks the administrative tasks to achieve this. For the CPaaS pipeline work see MON-3275.
  • Documentation work will be linked here too.

Why is this important?

• Various internal stakeholder are waiting for this install option
• This enables more complex setups, that CMO can not support

Scenarios

1. A operator author wants to integrate a prometheus stack in their system, without clashing with the CMO supplied stack

Acceptance Criteria

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

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. https://issues.redhat.com/browse/MON-3137

Open questions::

1. What is our support statement for this catalog entry

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>