Use architecture dependent images

[tolusha]

Signed-off-by: Anatolii Bazko abazko@redhat.com

Reference issue

https://issues.redhat.com/browse/CRW-1131

What does this PR do

Using architecture dependent images.

[tolusha]

/test v5-che-operator-olm-latest-changes-tests

[nickboldt]

Right now we only need the keycloak (RH-SSO) image to be named differently by arch, but this solution should work for ANY images we have to use in future which are openjdk/openj9 differentiated, even plugin & devfile registries, which right now are planned to be built with different references inside them, rather than being differently-named images.

Thus quay.io/crw/pluginregistry-rhel8:2.4 will have:

• for x, references to EAP and XP images w/ openjdk
• for z & p, references to EAP and XP images with openj9
  (but the published containers will all have the same name/tag in OSBS/RHCC/Quay)

So... +1, as this should unblock us from moving to the bundle format for operator-metadata and enable x/z/p arches too.

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: nickboldt, tolusha
To complete the pull request process, please assign
You can assign the PR to them by writing /assign in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[nickboldt]

Once this is merged for Che 7.18, the followup work for CRW 2.4 would be to:

• insert RELATED_IMAGE_keycloak_s390x = SSO for Z image
• insert RELATED_IMAGE_keycloak_ppc64le = SSO for Power image

into the csv for CRW 2.4.

Correct?

[flacatus]

/retest

[tolusha]

@nickboldt
Correct