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: Ok, so we know how our application is going to be _built_ and instantiated on OpenShift. But how are we going to use
  it? For this we need _services_. A _service_ identifies a set of pods (using labels) in order to proxy the connections
  it receives to them. Backing pods can be added to or removed from a service arbitrarily while the service remains
  consistently available, enabling anything that depends on the service to refer to it at a consistent internal address.
  
  Services are assigned an IP address and port pair that, when accessed, proxy to an appropriate backing pod. A service
  uses a label selector to find all the containers running that provide a certain network service on a certain port.
  
negative.code: oc policy add-role-to-group view system:serviceaccounts -n vertx-kubernetes-workshop
  ----
  
  The first instruction creates the project. The 3 last instructions grant 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, so let's deploy our
  first application.
  
  In the workshop source code, locate the `currency-3rdparty-service` and navigate to the directory in your terminal.
  Now issue the `mvn fabric8:deploy` command:
  
  [source, bash]
  ----
  