Epic Goal

• Operator maintainers to verify that their operators function correctly with OLMv1 before August 22, 2025. This is necessary because OLMv1, which was GA'ed in OCP 4.18, is a redesigned version of OLMv0 and is not 100% backward compatible.

https://docs.google.com/document/d/1UpBLZFGONj-e9aDTvWFdlGKLnaIhTZQr-wOWcs6lGCI/edit?pli=1&tab=t.0#heading=h.1kz9dp2t7g8c

The document provides detailed instructions on how to verify an operator, which involves configuring a cluster, creating a manifest, applying it to the cluster, and running existing test suites. It also asks for the results of the installation and runtime tests, along with a confirmation of support, to be reported back in a Jira issue linked to OCPSTRAT-2268.

Why is this important?

• This is necessary because OLMv1, which was GA'ed in OCP 4.18, is a redesigned version of OLMv0 and is not 100% backward compatible.

There could be subtle differences between OLMv0 and OLMv1, such as the lack of support for the OperatorConditions API in OLMv1 and differences in how upgrade edges are interpreted. And,some features, like support for webhook definitions and certain install modes, are not yet fully available in OLMv1.

Scenarios

1. ...

Acceptance Criteria (Mandatory)

• OpenShift Pipelines operator to run successfully on OLMV1
• ...

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. …

Open questions::

1. …

Done Checklist

• Acceptance criteria are met
• Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)
• User Journey automation is delivered
• Support and SRE teams are provided with enough skills to support the feature in production environment