Epic Goal

• Allow OLM V1 users to specify a version or versionRange when installing an operator through the Operator API.

Why is this important?

• Users want to be able to specify an exact version, a version range, or no version when installing and/or updating an operator. OLM V1 currently only supports an exact version.

• This has an implicit side effect on update policy: if a user doesn't want to update their operator, they may specify an exact version; otherwise, you can specify either a range or no version, and OLM will automatically update your operator.

• Among other things, completion of the work described in this brief will enable users to receive automatic updates, and also to limit automatic updates to a particular z-stream of an operator.

Previous Work (Optional):

• Technical Brief
• RFC

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>