Uploaded image for project: 'OpenShift Container Platform (OCP) Strategy'
  1. OpenShift Container Platform (OCP) Strategy
  2. OCPSTRAT-297

[customer portal/lab app] Display all RH Operator versions within the OCP catalog data for compatibility guidelines

XMLWordPrintable

    • Icon: Feature Feature
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • Operator Framework
    • False
    • Hide

      None

      Show
      None
    • False
    • OCPSTRAT-27Operators and Operator Lifecycle Management and Operator Hub
    • 75
    • 75% 75%
    • 0
    • 0

      Goals

      Display all compatible versions of Red Hat Operators to a particular OpenShift version so the customers can install/upgrade Red Hat Operators in/to a feasible version to stay within the support boundaries or get prepared before OpenShift upgrades.  

      Why is this important:

      Customers need clear guidance on the feasible Red Hat Operator versions so they can install and upgrade to stay within the support boundaries from Red Hat, or get their clusters prepared before the OpenShift upgrades.  

      Background, and strategic fit

      With the increasing usage and popularity of the Red Hat OpenShift Container Platform Operator Update Information Checker, we have gathered a new set of customer requirements that are beyond what the lab app currently provided.  

      The most frequent ask is about “knowing the Operator version(s) customers can safely install or upgrade to”.  In this scenario, customers may have certain tests or criteria in place before committing to installing/upgrading to a particular Operator version.  Hence, it is also important to display non-latest Operator versions (available in an update channel) from the OpenShift Operator catalog data.

      Another area for improvement is to include additional OpenShift catalog data for the lap app.  The lab app was previously created in the context of assisting customers to get prepared for the OpenShift Extended Update Support (EUS) upgrade from 4.8 to 4.10.  As we are marching toward the 4.12 GA, the lab needs to include catalog data from 4.11 and 4.12 as well.

      Requirements

      • The lab app renders non-latest/available Operator versions of an update channel from the catalog data.
      • Add OCP 4.11 and 4.12 catalog data as the filtering options
        • Include filtering options as a part of the URL for sending readers to this lab app with filters pre-populated per context.

      Previous Works:

      Customer Considerations

      • ...

            rhn-coreos-tunwu Tony Wu
            rhn-coreos-tunwu Tony Wu
            Jian Zhang Jian Zhang
            Matthew Werner Matthew Werner
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: