Epic Goal

• Ensure that users who install operators via OLM have an opportunity to know which operators are likely to work.

Why is this important?

• We make it easy to install operators into a running OpenShift deployment. Many of those operators are not going to support single-node deployments, because they require multiple replicas. We want to help users find operators that either explicitly support our topology API to manage their HA configuration or run with a singleton operand under all configurations.

Scenarios

1. As a user of a single-node OpenShift deployment, I want to find add-on operators that should work so that I can install and use them.

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>