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

Add annotation to operators supported in disconnected environments

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Done
    • Icon: Normal Normal
    • None
    • None
    • OLM
    • None
    • False
    • False
    • 0
    • 0% 0%
    • Undefined

      1. Proposed title of this feature request

      Add annotation to operators supported in disconnected environments

       

      2. What is the nature and description of the request?

      There is a list of operators supported in disconnected mode in KCS 4740011 [1], but that information is not shown for all operators in the OpenShift web console.
      Operators like ServiceMesh show that it works in disconnected environments, but others like Jaeger, Pipelines, Gitops and Elasticsearch don't.

       

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

      To have the information when trying to install the operator, and not in a different document [1].

       

      4. List any affected packages or components.

      As shown in the step 5 of the blog post in [2], there is an annotation to announce to the OperatorHub that the Operator runs in disconnected environments, so looks like each operator is responsible of that information (confirmed by [3]):

      operators.openshift.io/infrastructure-features: '["disconnected"]'
      

       

      [1] https://access.redhat.com/articles/4740011
      [2] https://www.openshift.com/blog/building-an-air-gap-friendly-operator
      [3] https://bugzilla.redhat.com/show_bug.cgi?id=1861262#c3

            DanielMesser Daniel Messer
            oarribas@redhat.com Oscar Arribas Arribas
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: