Until the jlink image scripts are shipped, during development we need to remember that the input imageStream needs to be adjusted to include development images.

This can be done by hand with something like

REGISTRY_AUTH_PREFERENCE=docker oc registry login
docker tag ubi9/openjdk-17:1.18 default-route-openshift-image-registry.apps-crc.testing/jlink1/ubi9-openjdk-17:1.18
docker push default-route-openshift-image-registry.apps-crc.testing/jlink1/ubi9-openjdk-17:1.18

Add a note to https://github.com/jboss-container-images/openjdk/blob/jlink-dev/templates/jlink/README.md to spell this out.

It might even be worth NOT suggesting importing the UBI9 image streams at all, and instead creating the one we want by hand from scratch and intentionally pushing the dev images to it, to remove the risk of accidentally putting the (non-jlink) GA images through the pipeline.