Uploaded image for project: 'Red Hat Advanced Cluster Management'
  1. Red Hat Advanced Cluster Management
  2. ACM-1964

UI and backend to handle hypershift API version change from v1alpha1 to v1beta1

XMLWordPrintable

    • Hypershift API version change from v1alpha1 to v1beta1
    • False
    • Hide

      None

      Show
      None
    • False
    • Green
    • Administer
    • To Do
    • 0% To Do, 0% In Progress, 100% Done

      Epic Goal

      • Hypershift HostedCluster and NodePool API version will change from v1alpha1 to v1beta1 in hypershift 4.12 (ACM 2.7). This epic is for the MCE console and backend to cope with the API version change.

      Why is this important?

      • UI to continue working with the new API version
      • Update backend documentations on how SD uses manifestwork with the hypershift APIs as payload

      Scenarios

      1. The hypershift operator upgrades HostedCluster and NodePool CRDs to the new version.
      2. Hypershift's mutation webhook can convert v1alpha1 to v1beta1.
      3. UI should be able to handle v1beta1 CRs.

      Acceptance Criteria

      • CI - MUST be running successfully with tests automated
      • Release Technical Enablement - Provide necessary release enablement details and documents.
      • ...

      Dependencies (internal and external)

      1. ...

      Previous Work (Optional):

      Open questions::

      Done Checklist

      • CI - CI is running, tests are automated and merged.
      • Release Enablement <link to Feature Enablement Presentation>
      • DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
      • DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
      • DEV - Downstream build attached to advisory: <link to errata>
      • QE - Test plans in Polarion: <link or reference to Polarion>
      • QE - Automated tests merged: <link or reference to automated tests>
      • DOC - Downstream documentation merged: <link to meaningful PR>

      ACM Epic Done Checklist

      See presentation and details.

      Update with "Y" if Epic meets the requirement, "N" if it does not,  or "N/A" if not applicable.

      • N/A FIPS Readiness
      • Y Works in Disconnected
      • N/A Global Proxy Support
      • N/A Installable to Infrastructure Nodes
      • Y No impacts to Performance and Scalability
      • N/A Backup and Restorable

              fxiang@redhat.com Feng Xiang
              rokejungrh Roke Jung
              Juliana Hsu Juliana Hsu (Inactive)
              Roke Jung Roke Jung
              David Huynh David Huynh
              Bradd Weidenbenner Bradd Weidenbenner
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: