Uploaded image for project: 'OpenShift Request For Enhancement'
  1. OpenShift Request For Enhancement
  2. RFE-5555

oc-mirror adds "cs" prefix while generating catalogsource name.

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Unresolved
    • Icon: Critical Critical
    • None
    • openshift-4.14, openshift-4.15
    • oc
    • False
    • None
    • False
    • Not Selected

      1. Proposed title of this feature request

      We should have one option when we use targetCatalog or something like this to set manual catalogsource name,  cs prefix should not be added by oc-mirror.

      2. Why does the customer need this? (List the business requirements here)

      It's creating impact for those customers who manage their environment using automation. 

      3. steps to re-produce this issue:

      A. Create ImageSetConfiguration with targetCatalog

      kind: ImageSetConfiguration
      apiVersion: mirror.openshift.io/v1alpha2
      archiveSize: 4
      storageConfig:
        registry:
          imageURL: private-registry:8443/test
          skipTLS: false
      mirror:
        operators:
        - catalog: registry.redhat.io/redhat/community-operator-index:v4.14
          targetCatalog: community-operator-index-1
          packages:
          - name: <any-operator-name>
            channels:
            - name: <channel-name> 

      And  mirror the images.  I was expecting my catalogsource name would be community-operator-index-1 but when i check i found it re-named as cs-community-operator-index-1 . There should be any way to avoid cs prefix?

      $ cat oc-mirror-workspace/results-1716359650/catalogSource-cs-community-operator-index-1.yaml 
      apiVersion: operators.coreos.com/v1alpha1
      kind: CatalogSource
      metadata:
        name: cs-community-operator-index-1 

              rhn-coreos-tunwu Tony Wu
              rhn-support-bshaw Bikash Shaw
              Votes:
              1 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated: