Uploaded image for project: 'OpenShift Console'
  1. OpenShift Console
  2. CONSOLE-2203

Users can select an Operator version when installing on the OperatorHub view

    XMLWordPrintable

Details

    • Epic
    • Resolution: Done
    • Major
    • None
    • None
    • OLM Screens
    • None
    • Allow install older Operator versions
    • OCPPLAN-8037OLM UI: Operator first-class experience
    • To Do
    • OCPPLAN-8037 - OLM UI: Operator first-class experience
    • Impediment
    • 100
    • 100% 100%

    Description

      Goal: OperatorHub/OLM users get a more intuitive UX around discovering and selecting Operator versions to install.

      Problem statement: Today it's not possible to install an older version of an Operator unless the user exactly nows the CSV semantic version. This is not exposed however through any API. `packageserver` as of today only shows the latest version per channel.

      Why is this important: There are many reasons why a user would want to choose not to install the latest version - whether it's lack of testing or known problems. It should be easy for a user to discovers what versions of an Operator OLM has in its catalogs and update graphs and expose this information in a consumable way to the user.

      Acceptance Criteria:

      • Users can choose from a list of "available versions" of an Operator based on the "selected channel" on the 'OperatorHub' page in the console.
      • Users can see/examine Operator metadata (e.g. descriptions, version, capability level, links, etc) per selected channel/version to confirm the exact version they are going to install on the OperatorHub page.
      • The selected channel/version info will be carried over from the 'OperatorHub' page to 'Install Operator' page in the console.
      • Note that "installing¬†an older version" means "no automatic update"; hence, when users select a non-latest Operator version, this implies the "Update" field would be changed to "Manual".

      Out of scope:

      • provide a version selector for updatres in case of existing installed operators

      Attachments

        Issue Links

          1.
          Docs Tracker Sub-task Closed Undefined Unassigned
          2.
          QE Tracker Sub-task Closed Undefined Unassigned
          3.
          TE Tracker Sub-task Closed Undefined Unassigned

          Activity

            People

              sgoodwin_redhat Steve goodwin
              rhn-coreos-tunwu Tony Wu
              Votes:
              0 Vote for this issue
              Watchers:
              13 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: