Uploaded image for project: 'OpenShift Virtualization'
  1. OpenShift Virtualization
  2. CNV-79858

[ operator-portfolio] [devops] CNV adjusting to OLM v1 & OCP5 (with smooth upgrade) - defining the scope (other teams will follow)

XMLWordPrintable

    • cnv-cluster-level-operator
    • Quality / Stability / Reliability
    • 77
    • Hide

      The work is understood and created in jira.

      Show
      The work is understood and created in jira.
    • Green
    • To Do
    • 100% To Do, 0% In Progress, 0% Done
    • dev-ready, doc-ready, po-ready, qe-ready
    • Hide

      2026-02-16:
      Needs grooming...

      Show
      2026-02-16: Needs grooming...

      Goal

      CNV devops should be OLM v1 ready. First, in order to be able to test CNV after it was installed by OLM v1, but also to allow customer start using OLM v1 instead of OLM v0 that is about to be deprecated.

      OLM v1 is different than v0 in many ways. The following are the most relevant changes:

      • The following CRs are not part of OLM v1 and won't be in use:
        • Subscription
        • CSV
        • InstallPlan
        • CatalogSource

      Instead, the OLM v1 uses a ClusterCatalog CR for the catalog - it's a cluster scoped type. To install a specific operator in v1, we'll use the ClusterExtension CR.

      • OLM v1 keep reconcile the resources from the CSV in the bundle image, like deployments.

      User Stories

      • Testing CNV installation with OLM v1.
        "As a project manager, I want validate that CNV can be installed with OLM v1, so that we could let customer to move to the next generation of the Operator Life-cycle Management, and to follow the operator portfolio requirements."
      • another user story

      Non-Requirements

      • List of things not included in this epic, to alleviate any doubt raised during the grooming process.

      Notes

      • Any additional details or decisions made/needed

          1.
          upstream roadmap issue Sub-task Closed Undefined Unassigned
          2.
          upstream design Sub-task Closed Undefined Unassigned
          3.
          upstream documentation Sub-task Closed Undefined Unassigned
          4.
          upgrade consideration Sub-task Closed Undefined Unassigned
          5.
          test plans in polarion Sub-task Closed Undefined Unassigned
          6.
          automated tests Sub-task Closed Undefined Unassigned
          7.
          downstream documentation merged Sub-task Closed Undefined Unassigned
          8.
          CNV QE DevOps Requirement/Enablement Sub-task Closed Undefined Unassigned

              dkeler@redhat.com Daniel Keler
              nunnatsa Nahshon Unna Tsameret
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: