Create deploying Quarkus applications to OpenShift guide by lift and shift the existing Deploying your Quarkus application to OpenShift with following changes:

• Release version
  There seem to be no version references in the guide.
  The release version is already updated using the QuarkusPluginVersion, ProductVersion, and ProductLongVersion attributes in common/attributes.adoc. Most of the version references in the guide should be handled using attributes substitutions.

• Using S2I to deploy Quarkus applications to OpenShift
• In the procedure in Chapter 6, add a step after Step 1:
  . Package your application:

  ./mvnw clean package
  

  Reason: the procedure describes a binary s2i build in which you deploy you application from a JAR file. You must package your application to generate the JAR file and push the generated Jar file to the Git repository before you can set up the binary build.

• In Chapter 6 Step 3, update the example showing the environment variables that must be set so that the app can be built and deployed to OpenShift with S2I. This change is necessary because the default packaging format changed to Fast JAR that uses a different file name and is stored in a separate subdirectory within the target/ directory of the Maven project
  The new example of the .s2i/environment file must contain the following variables:

  MAVEN_S2I_ARTIFACT_DIRS=target/quarkus-app
  S2I_SOURCE_DEPLOYMENTS_FILTER=app lib quarkus quarkus-run.jar
  JAVA_OPTIONS=-Dquarkus.http.host=_<host_server_ip_address>_
  AB_JOLOKIA_OFF=true
  JAVA_APP_JAR=/deployments/quarkus-run.jar