There are a number of options for which workflow to use for jlink integration in openShift

1. S2I has a runtime image flow. Jon tried to test this once and it did not seem to work (final application was layered on the builder image despite specifying --runtime-image) However this might have been an old s2i binary version, and/or the OpenShift internal S2I process probably work
2. OpenShift's BuildConfig and Dockerfile strategy with multi-stage builds (see e.g. this blog post])
3. Buildpacks, depending on where we are at with OpenShift support for that

Which one should we use?