Epic Goal

• Inform users about subscription requirements an optional operator has
• make it easy for OKE customers to filter for operators that are covered by an OKE subscription
• make it easy for OCP customers to filter for operators that are covered by OCP subscription

Why is this important?

• There is no information about additional subscription requirements on operators in a the OperatorHub today
• as a result a customer may easily fall into a situation where they are undersubscribed without any awareness of that being the case

Scenarios

1. A cluster admin can filter the OperatorHub catalog view for operators that are included in OKE (require OKE or OCP subscription) vs. the ones included in OCP (require a OCP subscription)
2. A cluster admin can learn about additional subscription requirements via visual badges on operator tiles
3. A cluster admin can learn about additional subscription requirements in the detail views of OperatorHub entries

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. KODIAK-313
2. CWFCONF-454
3. CLOUDWF-5288

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>