anchor.diff:  ./mvnw clean package -Dquarkus.kubernetes.deploy=true
   ----
   
  +TIP: If you want to test your application immediately then set the `quarkus.openshift.route.expose` config property to `true` to <<exposing_routes,expose the service automatically>>, e.g. add `-Dquarkus.openshift.route.expose=true` to the command above.
  +
   This command will build your application locally, then trigger a container image build and finally apply the generated OpenShift resources automatically.
   The generated resources use 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:
  -
  +You can use the OpenShift web console to verify that the above command has created an image stream, a service resource and has deployed the application.
  +Alternatively, you can run the following OpenShift CLI commands:
   [source,bash,subs=attributes+]
   ----
   oc get is <1>
  
positive.code: 
  Some examples are provided in the sections below:
  
  === Exposing Routes
  
  To expose a `Route` for the Quarkus application:
  
negative.code: <2> Get the list of pods.
  <3> Get the list of Kubernetes services.
  
  Note that the service is not exposed to the outside world by default.
  So unless you've used the `quarkus.openshift.route.expose` config property to expose the created service automatically you'll need to expose the service manually.
  
  .Expose The Service - OpenShift CLI Example
  [source,bash,subs=attributes+]
  ----
  oc expose svc/greeting <1>
  