anchor.diff:  ----
   
   The build that will be performed is an s2i binary build. The input of the build is the jar that has been built locally and the output of the build is an ImageStream that is configured to automatically trigger a deployment.
  +
  +To deploy the container image created in the above step to OpenShift, follow these commands:
  +[source, subs=attributes+]
  +----
  +oc get is
  +oc new-app --name=greeting <project>/openshift-quickstart:1.0-SNAPSHOT
  +oc get svc
  +oc expose svc/greeting
  +oc get routes
  +curl http://<route>/greeting
  +----
  +
  +In the above, `oc get is` will list the image stream created.  It should be tagged as <project>/openshift-quickstart:1.0-SNAPSHOT.
  +
  +Similarly, `oc get route` will list the route URL for the exposed service "greeting" so that you can use it to test the application.
   
   === Non S2i Builds
   
  
positive.code: The configuration items that are available can be found in: `io.quarkus.kubernetes.deployment.OpenShiftConfig` class.
  Furthermore, the items provided by `io.quarkus.deployment.ApplicationConfig` affect the OpenShift resources.
  
  === Building
  
  Building is handled by the link:container-image#s2i[container-image-s2i] extension. To trigger a build:
  
  [source, subs=attributes+]
  
negative.code: * JDK 1.8+ installed with `JAVA_HOME` configured appropriately
  * Apache Maven {maven-version}
  * access to an OpenShift cluster (Minishift is a viable option)
  * OpenShift CLI (Optional. Only required for manually deploying)
  
  == Creating the Maven project
  
  