anchor.diff:  
   [source]
   ----
  -quarkus.kubernetes.deployment-target=kubernetes, openshift
  +quarkus.kubernetes.deployment-target=kubernetes,openshift
   ----
   
   Following the execution of `./mvnw package` you will notice amongst the other files that are created, two files named
   `openshift.json` and `openshift.yml` in the `target/kubernetes/` directory.
   
  -These manifests can be deployed as is to a running cluster, using kubectl:
  -
  -[source]
  ----
  +These manifests can be deployed as is to a running cluster, using `kubectl`:
  +
  +[source]
  +----
   kubectl apply -f target/kubernetes/openshift.json
  ----
  +----
   
   Openshift users might want to use `oc` instead of `kubectl`:
   
   [source]
  ----
  +----
   oc apply -f target/kubernetes/openshift.json
  ----
  +----
   
   
   NOTE: Quarkus also provides the link:deploying-to-openshift[OpenShift] extension. This extension is basically a wrapper around the Kubernetes extension and
  
positive.code: quarkus.kubernetes.env-vars.my-env-var.secret=my-secret
  ----
  
  ===== Environment variables from ConfigMap
  
  To add all key/value pairs of a `ConfigMap` as environment variables just apply the following configuration:
  
negative.code: 
  === Add readiness and liveness probes
  
  By default, the Kubernetes resources do not contain readiness and liveness probes in the generated `Deployment`. Adding them however is just a matter of adding the SmallRye Health extension like so:
  
  [source,xml]
  ----
  