Epic Goal

The Operator Framework team is pleased to announce that OLM v1, the next generation of Operator Lifecycle Manager, has reached general availability (GA) in its initial phase with the OpenShift 4.18 release.

OLM v1 delivers significant improvements for managing operators and complex workloads on OpenShift, including fully declarative, GitOps-friendly workflows, precise control over update paths, and simplified user-facing APIs.

OLM v1’s initial GA release in OpenShift 4.18 supports a select set of operators from the default Red Hat Operator catalogs.  We are actively expanding compatibility across the operator ecosystem, starting with operators that meet the specified criteria due to current limitations.

To ensure seamless interoperability, we encourage operator teams that meet the test criteria to integrate testing against OLM v1 into your release CI pipelines.  Instructions for setting up these tests can be found in this document: Verifying Published Content with OLM v1.

We recommend prioritizing testing against the downstream OLM v1 GA releases in OpenShift 4.18.  Once validated against 4.18, please continue testing against the downstream OLM v1 master branch, which receives nightly builds.

For any questions, please contact the Operator Framework engineering team in the #forum-ocp-operator-fw Slack channel.  We also plan to launch an Operator Framework Office Hour soon, providing another opportunity for discussion and feedback.  We will share details about the Office Hour once available.

Why is this important?

...

Scenarios

...

Acceptance Criteria

...

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 - Doc issue opened with a completed template. Separate doc issue
  opened for any deprecation, removal, or any current known
  issue/troubleshooting removal from the doc, if applicable.
• Considerations were made for Extended Update Support (EUS)