Epic Goal

• Enable OLM support for different runtimes (OLM/registry+v1, Helm/Chart, PKO, etc.)

Why is this important?

• OLM has the goal to support different content packaging strategies. These will need to be handled by their own runtime

Scenarios

1. Install registry+v1 bundle
2. Install Helm Chart packaged operator
3. Install PKO package
4. Inter-format upgrade edges (go from registry+v1 to Helm Chart, for example)

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• RFC Written and accepted
• Interface describe and agreed on with other stakeholders (e.g. ecosystem team)
• registry+v1 reference runtime implementation created and operator-controller refactored to use it
• e2e tests should continue working after the refactor with minimal changes (if any at all)

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>