Uploaded image for project: 'Red Hat 3scale API Management'
  1. Red Hat 3scale API Management
  2. THREESCALE-11927

Do we need to downgrade the 3scale Operator from 2.15 to 2.14 during OpenShift upgrade from 4.18 to 4.19

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Minor Minor
    • 2.15.4 GA
    • 2.15.0 GA, 2.14.4 GA
    • Apicast Operator
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started

      While planning an OpenShift cluster upgrade from 4.18 to 4.19, we observed that the default version of the 3scale Operator available in the OperatorHub changes unexpectedly:

      • On OpenShift 4.18, the default 3scale Operator version is 2.15.
      • On OpenShift 4.19, the default 3scale Operator version is 2.14.

      This raises a concern about whether 3scale Operator 2.15 is supported on OCP 4.19, and whether the downgrade is intentional or a packaging/catalog issue.

      This impacts our cluster upgrade path since workloads currently rely on 3scale Operator 2.15. Confirmation of supportability and a clear upgrade path are needed before proceeding.

              Unassigned Unassigned
              rhn-support-hthakare Harshal Thakare
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: