Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-48837

As an oc-mirror user, I'd like to have ClusterCatalog resource generated for operator catalogs

XMLWordPrintable

    • None
    • CLID Sprint 265, CLID Sprint 266
    • 2
    • False
    • Hide

      None

      Show
      None
    • N/A
    • Release Note Not Required
    • In Progress

      This is a clone of issue OCPBUGS-45161. The following is the description of the original issue:
      —
      Description of problem:

      OLMv1 is being GA'd with OCP 4.18, together with OLMv0. The long(ish)-term plan right now is for OLM v0 and v1 to be able to coexist on a cluster. However, their access to installable extensions is through different resources. v0 uses CatalogSource and v1 uses ClusterCatalog. We expect to see catalog content begin to diverge at some point, but don't have a specific timeline for it yet.

oc-mirror v2 should generate ClusterCatalog YAML along with CatalogSource YAML.

We also work with docs team to document ClusterCatalog YAML is only needed to be applied when managing Operator catalogs with OLM v1.

      Version-Release number of selected component (if applicable):

          4.18+

      How reproducible:

          always

      Steps to Reproduce:

          1.
    2.
    3.

      Actual results:

      Expected results:

          ClusterCatalog resource is generated for operators.

      Additional info:

          OLMv1 currently only works for a small subset of operators in the catalog.

              rdossant Rafael Fonseca dos Santos
              openshift-crt-jira-prow OpenShift Prow Bot
              Rama Kasturi Narra Rama Kasturi Narra
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: