Uploaded image for project: 'OCMUI - OpenShift Cluster Manager UI'
  1. OCMUI - OpenShift Cluster Manager UI
  2. OCMUI-4080

Prepare console.redhat.com for OpenShift 5

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • Core UI
    • None
    • Prepare console.redhat.com for OpenShift 5
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • False
    • To Do
    • OCPSTRAT-2797Enable OCP 4.22 -> OCP 5.0 updates
    • 100% To Do, 0% In Progress, 0% Done

      I'm not familiar enough with console.redhat.com to be confident in auditing myself, but at least this uhc-portal code will need adjusting, depending on what PLMCORE-14942 does with https://access.redhat.com/product-life-cycles/api/v1/products. Perhaps it will be just changing the product name used in the query from OpenShift Container Platform 4 to OpenShift Container Platform? That would be straightforward. But maybe PLMCORE-14942 will move in a different direction. And maybe there are other places in OCMUI code that currently assume that we're talking about OCP 4, that will need softening now that we might be talking about other major versions as well.

              Unassigned Unassigned
              trking W. Trevor King
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: