anchor.diff:  quarkus.container-image.builder=jib
   ----
   
  -=== Deploying
  -
  -To trigger a deployment:
  +=== Build and Deploy (in a single step)
  +
  +If the OpenShift extension was not included during the bootstraping of the project nor was it added subsequently (check pom.xml file for it), then it can be added like this:
  +
  +[source, subs=attributes+]
  +----
  + ./mvnw quarkus:add-extension -Dextensions="openshift"
  +----
  +
  +To trigger a build and deployment in a single step:
   
   [source, subs=attributes+]
   ----
   ./mvnw clean package -Dquarkus.kubernetes.deploy=true
   ----
   
  -The command above will trigger a container image build and will apply the generated OpenShift resources, right after.
  +The aforementioned command will build a jar file locally, trigger a container image build and then apply the generated OpenShift resources.
   The generated resources are using OpenShift's `DeploymentConfig` that is configured to automatically trigger a redeployment when a change in the `ImageStream` is noticed.
   In other words, any container image build after the initial deployment will automatically trigger redeployment, without the need to delete, update or re-apply the generated resources.
  +
  +To confirm the above command has created an image stream, a service resource and has deployed the application (has a pod running), apply these commands:
  +
  +[source, subs=attributes+]
  +----
  +oc get is
  +oc get pods
  +oc get svc
  +----
  +
  +To expose the created service to a route and test it:
  +
  +[source, subs=attributes+]
  +----
  +oc expose svc/greeting
  +oc get routes
  +curl http://<route>/greeting
  +----
   
   === Customizing
   
  
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
  
  