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

Hypershift operator continuous delivery to Service Delivery

    XMLWordPrintable

Details

    • Hypershift operator continuous delivery to Service Delivery
    • False
    • None
    • False
    • Not Selected
    • To Do
    • 100
    • 100% 100%

    Description

      Epic Goal

      • We want to set up a flow:
        • to allow the Hypershift team to provide the Git sources of all 8 container images that make up the hypershift operator to ACM CICD
        • for ACM CICD build downstream images based on the input Git sources and extract image manifests of those 8 hypershift container images
        • push the image stream configmap to some Gitlab repo for SD fleet manager to take and apply it to a service cluster

      Why is this important?

      • This allows the hypershift operator delivery schedule to be independent of ACM 
      • This allows to upgrade only the hypershift operator without having to re-install or upgrade ACM when no fix is required for ACM

      Scenarios

      1. The hypershift Dev team wants to roll out a new version of hypershift operator to SD
      2. The hypershift Dev team commits a set of Git sources that make up the new version of hypershift to ACM CICD pipeline  (https://issues.redhat.com/browse/HOSTEDCP-665)
      3. ACM CICD pipeline builds new set of hypershift container images
      4. ACM CICD extracts the hypershift images manifests and build a image override configmap (example documented here https://github.com/rokej/hypershift-addon-operator/blob/placement_score/docs/upgrading_hypershift_operator.md#overriding-the-hypershift-operator-image-references-1) and commits it to Gitlab for SD fleet-manager to consume

      Acceptance Criteria

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

      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>

      Attachments

        Issue Links

          Activity

            People

              Gurney.Buchanan@ibm.com Gurney Buchanan
              rokejungrh Roke Jung
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: