Open Jdubrick opened 5 months ago
Currently talking with the ocp team about making our workloads work with arm. Currently there may be a limitation on their end about us building the arm64 image ephemerally and sending it in the payload which I believe would affect how our entire ci-operator is setup if that had to change. I'll leave updates here as I receive them.
WIP PR opened for their workloads configs here: https://github.com/openshift/release/pull/52962
Marking as blocked as ocp team is looking into if we are able to do what we need with arm64 through the ci operator. Currently they have "support" for arm64 through a workaround but are unsure if they have support for building arm64 images on the fly which is what we need for our PR checks.
Blocked by: https://issues.redhat.com/browse/DPTP-4054
Moving to backlog - Been in waiting for a while and no updates on blocking issue
Which area is this issue related to?
/area ci /area registry
Issue Description
The devfile index is now supported for multiple architectures. As part of our plan to move our workloads on openshift ci to arm64 nodes the
.ci/openshift_integration.sh
script as part ofdevfile/registry
will need to be altered so it does not hardcode amd64 dependencies. The fix for that can follow what was done in other scripts with an optional argument being passed alongside the script. Additionally, the commands setup inci-operator
for the registry tests will also need to be changed to support aarch64 instead of x86_64.Acceptance Criteria
Step 1:
.ci/openshift_integration.sh
script altered to allow for amd64 or arm64Step 2 (Depends on step 1):
ci-operator
commands changed to accommodate the changs to the above script