anchor.diff:  - link:container-image#jib[Jib]
   - link:container-image#s2i[s2i]
   
  -Each time deployment is requested, a container image build will be implicitly triggered (no additional properties are required).
  +Each time deployment is requested, a container image build will be implicitly triggered (no additional properties are required when the Kubernetes deployment has been enabled).
   
   === Deploying
   
   When deployment is enabled, the kubernetes extension will selected the resources specified by `quarkus.kubernetes.deployment.target` and deploy them.
  -This assumes that a `.kube/config` is available in your user directory that points to a real kubernetes cluster.
  +This assumes that a `.kube/config` is available in your user directory that points to the target kubernetes cluster.
   In other words the extension will use whatever cluster `kubectl` uses. The same applies to credentials.
   
   At the moment no additional options are provided for further customization.
  
positive.code:     -DprojectArtifactId=kubernetes-quickstart \
      -DclassName="org.acme.rest.GreetingResource" \
      -Dpath="/greeting" \
      -Dextensions="kubernetes"
  cd kubernetes-quickstart
  ----
  
  
negative.code: }
  ----
  
  An important thing to note about the `Deployment` is that is uses `yourDockerUsername/test-quarkus-app:1.0-SNAPSHOT` as the container-image of the `Pod`.
  The name of the image is controlled by the `Jib` extension and can be customized using the usual `application.properties`.
  
  For example with a configuration like:
  
  