Closed didierofrivia closed 2 weeks ago
:warning: Please install the to ensure uploads and comments are reliably processed by Codecov.
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 61.78%. Comparing base (
05fddaa
) to head (ba8571b
).
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Hi @didierofrivia looks like after the modifications made to the catalog.mk file the matrix approach is no longer required as its working fine on s390x and ppc64le. Cheers
This PR aims to solve the issue of building catalogs for different architectures using just buildah, as reported in https://github.com/Kuadrant/authorino-operator/pull/214#issuecomment-2373038118 . It uses a matrix strategy in order to assert the right OPM base image is set in the catalog Dockerfile and build accordingly. It accomplish this having 2 different jobs, the original one is kept, expanded to the other 2 missing archs, and a dedicated one was created to explicitly include the opm version and architecture desired. The later one will create additional catalog images of the form
authorino-operator-catalog:{tag}-{arch}
Notes:
It was generated with the
latest
tag ofopm
. When pulling an specific platform you get:It was generated with the
v1.48.0-{ARCH}
tag ofopm
When pulling a catalog image from the specific multi arch job:The original (now modified) job should work, since buildah is using the
latest
tag that it's built multi platform too https://quay.io/repository/operator-framework/opm?tab=tags&tag=latest... but apparently it doesn't (?) hence the explicit multi arch job. @R3hankhan123 needs to validate this.Other attempts made:
uraimo/run-on-arch-action@v2
The issue was that the dockerfile was generated by a x86 builder, instead of a multiarch one