anchor.diff:  
   NOTE: When using the `quarkus-container-image-jib` extension to build a container image, then any label added via the aforementioned property will also be added to the generated container image.
   
  -====  Annotations
  +==== Annotations
   
   Out of the box, the generated resources will be annotated with version control related information that can be used either by tooling, or by the user for troubleshooting purposes.
   
  
positive.code:     </dependency>
  ----
  
  By adding these dependencies, we enable the generation of Kubernetes manifests each time we perform a build while also enabling the build of a container image.
  For example, following the execution of `./mvnw package` you will notice amongst the other files that are created, two files named
  `kubernetes.json` and `kubernetes.yml` in the `target/kubernetes/` directory.
  
  If you look at either file you will see that it contains both a Kubernetes `Deployment` and a `Service`.
  
negative.code: }
  ----
  
  The generated manifest can be applied to the cluster from the project root using `kubectl`:
  
  [source]
  ----
  kubectl apply -f target/kubernetes/kubernetes.json
  ----
  
  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`.
  