Value Statement

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.

Definition of Done for Engineering Story Owner (Checklist)

• Produce data about our operators

Development Complete

• NA

Tests Automated

• Not part of the spike

Secure Design

• [ ] Security has been assessed and incorporated into your threat model.

Multidisciplinary Teams Readiness

• [ ] Create an informative documentation issue using the [Customer
  Portal_doc_issue template](
  https://github.com/stolostron/backlog/issues/new?assignees=&labels=squad%3Adoc&template=doc_issue.md&title=),
  and ensure doc acceptance criteria is met. Link the development issue to
  the doc issue.
• [ ] Provide input to the QE team, and ensure QE acceptance criteria
  (established between story owner and QE focal) are met.

Support Readiness

• [ ] The must-gather script has been updated.