feat: support arm64 install on csv #213
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
We already build the arm64 image for the binary, bundle and catalog
authorino-operator/.github/workflows/build-images.yaml
Line 66 in 82e7719
authorino-operator/.github/workflows/build-images.yaml
Line 143 in 82e7719
authorino-operator/.github/workflows/build-images.yaml
Line 224 in 82e7719
However, we do not set allowing this install on the CSV. This prevents the catalog from showing on OperatorHub if we want to verify the catalog install via local Openshift platforms such as CRC if the local environment is using the
arm64architecture.This changes adds
arm64as a supported architecture on the CSV to allow for installing the image/bundle/catalog to this architecture