This only concerns templates in our eap72 ubi8 jdk11 repository: https://github.com/jboss-container-images/jboss-eap-7-openshift-image/tree/eap72-openjdk11-ubi8, because according to my latest information, we're only going to support the UBI8 JDK 11 image.

Some of our templates reference RH images, at least some of which don't yet have a public s390x build.

amq-broker-72-openshift:1.1
redhat-sso73-openshift:1.0
jboss-datavirt63-driver-openshift:1.1

To complete our Z-series offering, RH also needs to provide those images. In EAP, we need to think about two things:

• Are these images going to be available at the same time as EAP is going to be certified with s390x?
• Are they going to be certified at the same time? If not, how are we going to handle that?
• Do we need any changes in our templates? (I don't think that should be necessary from the technical perspective, but I'd like to have it confirmed).

For testing purposes, QE also needs testing images and instructions on how to use them with our templates - though this is probably a question on the teams which provide the above-mentioned images.