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

Provide a singular tool or method (or API!) to show supportability and compatibility of OpenShift operators and layered products

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • Documentation, OLM
    • None
    • False
    • None
    • False
    • Not Selected

      1. Proposed title of this feature request

      Provide a singular tool or method to show supportability and compatibility of OpenShift operators and layered products

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

      When attempting to deploy layered OpenShift offerings AND operators it can be hard to know which versions are compatible and/or support with which. 

      Currently you can track Operator lifecycles on one page (https://access.redhat.com/support/policy/updates/openshift_operators  But that just lists each Operator independently. 

      Some products have their own support matrices, such as this one for ACM: https://access.redhat.com/articles/7086905 but they can be hard to maintain and tend not to include operators or layered products outside their immediate impact.

      What would help if there's an interactive "wizard" of some sort where you can choose your OCP release and then the various pieces you are using with it. So you could choose an operator and its version, or a layered product and its version, and the tool would be able to validate supportability of the pieces with each other. It could then cough up a warning, perhaps even give it a quantified risk level, so that customers could easily understand what releases work with which.

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

      Customers want to use supported software.
      Customers want to layer software (and we want them to).
      The intricacies of using different operators and layered product suites makes it very hard to track, at the customer level, all the comparabilities.
      Customer don't have time to sort this out so have to ask.
      Field teams also cannot keep up, so they have to ask.
      Improved efficiency and self service on this would allow us all to focus on more important things, which is good for our customers!

      4. List any affected packages or components.
      All 😬

              rhn-coreos-tunwu Tony Wu
              asimonel August Simonelli
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: