Uploaded image for project: 'OpenShift Builds'
  1. OpenShift Builds
  2. BUILD-1471

Multi-Arch Container Builds

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • shipwright
    • None
    • Multi-arch builds
    • False
    • Hide

      None

      Show
      None
    • False
    • Not Selected
    • In Progress
    • SECFLOWOTL-83 - Multi-arch builds in Shipwright
    • 0% To Do, 0% In Progress, 100% Done

      Epic Goal

      Build images for multiple architectures (e.g. x86 and Arm) on a multi-arch compute (heterogeneous) clusters using a Shipwright Build.

      Why is this important?

      OpenShift supports multi-arch compute clusters where worker nodes with different architectures (e.g. x86, Arm) are available within a single cluster. Building applications for multiple architectures allows customers to make deployment decisions based on economics and efficiency criteria.

      Acceptance Criteria (Mandatory)

      • A Shipwright build supports building images for multiple architectures that are available within the cluster
      • The images for multiple architectures are pushed to a manifest list in a registry
      • 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):

      1. …

      Open questions::

      1. …
      •  

      Done Checklist

      • Acceptance criteria are met
      • Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)
      • User Journey automation is delivered
      • Support and SRE teams are provided with enough skills to support the feature in production environment

      Who

      What

      Reference
      DEV Upstream roadmap issue <link to GitHub Issue>
      DEV Upstream code and tests merged <link to meaningful PR or GitHub Issue>
      DEV Downstream code and tests merged <link to meaningful PR or GitHub Issue>
      QE Automated tests merged <link or reference to automated tests>
      DOC Downstream documentation merged <link to meaningful PR>
      DEV Technical Enablement (slides, demos) prepared <link to presentation, videos>

              Unassigned Unassigned
              rh-ee-ssadeghi Siamak Sadeghianfar
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: