anchor.diff:  
   There are different types of builds. You can create a `Docker` build taking a `Dockerfile` as parameter. The
   resulting image is generated by _building_ the `Dockerfile`. OpenShift also provides the concept of S2I (Source to
  -Image) as a tool to provide reproducible image. In this lab, we are going to use S2I with binary content. We are
  -going to build the application on our machine and push the resulting artifact (_fat jar_) as input of a S2I build.
  -This build creates an image starting the application.
  +Image) as a tool to provide reproducible images. In this lab, we are going to use S2I with binary content. We are
  +going to build the application on our machine and push the resulting artifact (a _fat jar_) as input to an S2I build.
  +This build creates an image for starting the application.
   
   image::openshift-build-process.png[OpenShift Build Process, 800]
   
  
positive.code: oc policy add-role-to-group view system:serviceaccounts -n vertx-kubernetes-workshop
  ----
  
  The first instruction creates the project. The 3 last instructions grants permissions in order to use all the
  OpenShift capabilities.
  
  In the OpenShift Web Console, you should see the newly created project. Click on it. It's empty, let's deploy our
  first application.
  
  In the workshop source code, locate the `currency-3rdparty-service`, and navigate in the directory in your terminal.
  Then issue the `mvn fabric8:deploy` command:
  
  [source, bash]
  ----
  
negative.code: ----
  
  The `fabric8 maven plugin` is a Maven Plugin facilitating the deployment of OpenShift applications. The `:deploy`
  mojo packages the application and triggers the S2I build described above.
  
  In your browser, check the content of the project. You should see something like:
  
  image::openshift-first-deployment.png[First deployment, 1024]
  
  
  Click on the route url and you should see `ok`.  This indicates that your first application was successfully deployed.
  
  
  