Uploaded image for project: 'OpenShift GitOps'
  1. OpenShift GitOps
  2. GITOPS-2442

Upstream changes: Add linux/arm64 (and possibly darwin/arm64 and windows/arm64) builds to kam

    XMLWordPrintable

Details

    • Story
    • Resolution: Done
    • Major
    • 1.8.0
    • None
    • Productization
    • None
    • 5
    • False
    • None
    • False
    • OCPPLAN-8226 - OpenShift Addons support for Arm
    • GITOPS Sprint 229

    Description

      Story (Required)

      As a user trying to install and deploy OpenShift GitOps on ARM workloads, I want to do it successfully.

      The goal of this story is to enable all upstream component to build ARM container images and binaries.

      Background (Required)

      We need to identify all images built and consumed in the upstream that require ARM to be enabled. We need to required changes to build multi-arch include ARM architecture. This also include kam CLI.

      Out of scope

      midstream and downstream components

      Approach (Required)

      • consult upstream_sources.yaml  for a list of upstream sources that built in CPaaS
      • review the changes we had during the effect to enable Power/Z multi-arch support

       

      Dependencies

      <Describes what this story depends on. Dependent Stories and EPICs should be linked to the story.>

      Acceptance Criteria (Mandatory)

      • All upstream components are enabled with ARM architecture including kam CLI

       

      INVEST Checklist

      Dependencies identified

      Blockers noted and expected delivery timelines set

      Design is implementable

      Acceptance criteria agreed upon

      Story estimated

      Legend

      Unknown

      Verified

      Unsatisfied

      Done Checklist

      • Code is completed, reviewed, documented and checked in
      • Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
      • Continuous Delivery pipeline(s) is able to proceed with new code included
      • Customer facing documentation, API docs etc. are produced/updated, reviewed and published
      • Acceptance criteria are met

      Attachments

        Issue Links

          Activity

            People

              yselkowi@redhat.com Yaakov Selkowitz
              wtam_at_redhat William Tam
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: