Uploaded image for project: 'OpenShift Container Platform (OCP) Strategy'
  1. OpenShift Container Platform (OCP) Strategy
  2. OCPSTRAT-1375

[Tech Preview phase III] Next-gen OLM (OLM v1)

XMLWordPrintable

    • BU Product Work
    • False
    • Hide

      None

      Show
      None
    • False
    • OCPSTRAT-27OLM V1: Operators, Operator Lifecycle Management, and Operator Hub
    • 0% To Do, 0% In Progress, 100% Done
    • 0
    • Program Call
    • TE should be grouped with OCPSTRAT-984; TE for TP should be done to increase exposure to CEE before the roll-out of V1 to all customers.
    • Operator Framework

      Feature Overview (aka. Goal Summary)  

      This Tech Preview release grants early access to upcoming features in the next-generation Operator Lifecycle Manager (OLM v1).  Customers can now test these functionalities and provide valuable feedback during development.

      Goals (aka. expected user outcomes)

      Highlights of OLM v1 Preview:

      • Terminology shift: Operators and Catalogs are now called ClusterExtensions and ClusterCatalogs within the API.
      • Deprecation notices: ClusterExtension APIs now indicate deprecated packages, channels, and bundles.
      • Enhanced statuses: ClusterExtension APIs now provide the specific bundle name, version, and clearer health information for a better user experience.
      • Legacy/custom upgrade edge support: OLM v1 offers full compatibility with existing upgrade edges in the catalog content (`skips`, `skip ranges`, and `replaces`).

      Requirements (aka. Acceptance Criteria):

      All the expected user outcomes and the acceptance criteria in the engineering epics are covered.

      Background

      Leveraging learnings and customer feedback since OCP 4's inception, OLM v1 is designed to be a major overhaul.

      With OpenShift 4.16, we are one step closer to the highly anticipated general availability (GA) of the next-generation OLM.  

      • See the OCPSTRAT feature for OLM v1 GA:
        OCPSTRAT-1347 [GA release] Next-gen OLM (OLM v1)

      Documentation Considerations

      • Terminology shift: [TP release] Docs introduce Operators and Catalogs that are now called ClusterExtensions and ClusterCatalogs within the API.
      • Deprecation notices: [TP release] Docs introduce ClusterExtension APIs now indicate deprecated packages, channels, and bundles.
      • Enhanced statuses:  [TP release] Docs introduce ClusterExtension APIs now provide the specific bundle name, version, and clearer health information for a better user experience.
      • Legacy/custom upgrade edge support:  [TP release] Docs introduce now OLM v1 offers full compatibility with existing upgrade edges in the catalog content (`skips`, `skip ranges`, and `replaces`).

      Relevant upstream CNCF OLM v1 PRs:

              rhn-coreos-tunwu Tony Wu
              rhn-coreos-tunwu Tony Wu
              Jian Zhang Jian Zhang
              Matthew Werner Matthew Werner
              Joe Lanford Joe Lanford
              Tony Wu Tony Wu
              Eric Rich Eric Rich
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: