[Spike] Investigate CI Workloads And Images That Can Be Migrated To Arm64 / Multi-Arch

Jdubrick commented 2 weeks ago

Which area/kind this issue is related to?

/area ci

Issue Description

The goal of this issue is to determine which of our Openshift CI Workloads are compatible with Arm64 and which are not. Additionally, it would be worthwhile to ensure our image builds can support multiple architectures moving forward. The goal is to migrate some or all of these workloads to Arm64 architecture. Dockerfiles will need to be investigated to ensure that they can be used to build both linux/amd64 and linux/arm64 images.

Currently the following repositories and nightly runs have jobs running on Openshift CI:

In addition to the above repositories, the following investigation has been done prior to this issue:

OCI Registry
- Builds cleanly
Devfile Index
- Current golang builder image does not support arm64
- Newer SHAs for 1.19 alpine image provide this support
Registry Viewer
- Requires env variable for linux/arm64 to build for arm64
Registry Operator
- Builds cleanly
Devfile Integration Tests
- Docker used for running the tests appears to download x86 binaries during build, this forces it to be amd64

It would also be worthwhile to look into the remaining devfile repositories, such as registry-support to see if there are any jobs that would benefit from having multi-arch support as well.

Podman appears to have something similar to Docker's buildx that can be referenced here: https://developers.redhat.com/articles/2023/11/03/how-build-multi-architecture-container-images#

Acceptance Criteria

[x] Repositories investigated for migration to arm64 or multi-arch support
[x] Issues created for accomplishing the multi-arch work and added to https://github.com/devfile/api/issues/1492

Jdubrick commented 5 days ago

See https://github.com/devfile/api/issues/1492#issuecomment-2108772391 for created issues from investigation.

Jdubrick commented 5 days ago

Sizing 3 points retrospectively.

devfile / api