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

Consolidate Operator tiles between “Certified” and “Marketplace” offerings in OperatorHub

XMLWordPrintable

    • None
    • Product / Portfolio Work
    • None
    • False
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      1. Proposed title of this feature request

      Consolidate Operator tiles between “Certified” and “Marketplace” offerings in OperatorHub

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

      The customer wants to have a consolidated view of an Operator if provided in both “Certified” and “Marketplace” offerings in OperatorHub so the users can easily see, understand, and decide which offer they want to proceed with. 

      There are cases that a partner product in OperatorHub is provided through two different variations: Red Hat Certified and Red Hat Marketplace. 

      • Red Hat Certified - Offers Level 1 support calls
      • Red Hat Marketplace - Offers commercial features around the consumption experience (e.g. raising support calls, requesting trials, etc)

      Currently, in OperatorHub, these two variations are each displayed in their own tiles with a pill-like “Marketplace” badge/label attached to the Red Hat Marketplace offering. 

      While the “Marketplace” badge/label helps differentiate the two offerings to some degree, the similar-looking two tiles may cause confusion for consumers and not sure about which offerings they should choose.

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

      The customer wants end-users can easily see, understand, and decide between “Certified” and “Marketplace” Operator offerings in OperatorHub. (e.g. which MongoDB operator should I use?)

      4. List any affected packages or components.

      OCP Console 

              rhn-coreos-tunwu Tony Wu
              rhn-coreos-tunwu Tony Wu
              None
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved:
                None
                None