anchor.diff:  quarkus.container-image.group=<project/namespace name>
   ----
   
  -===== Validation
  +==== Validation
   
   A conflict between two definitions, e.g. mistakenly assigning both a value and specifying that a variable is derived from a field, will result in an error being thrown at build time so that you get the opportunity to fix the issue before you deploy your application to your cluster where it might be more difficult to diagnose the source of the issue.
   
  
positive.code:         optional: false
  ----
  
  ===== Environment variables from ConfigMap
  
  To add all key/value pairs from `ConfigMap` as environment variables just apply the following configuration, separating each
  `ConfigMap` to be used as source by a comma (`,`):
  
negative.code: quarkus.openshift.env.fields.foo=metadata.name
  ----
  
  ==== Using Deployment instead of DeploymentConfig
  Out of the box the extension will generate a `DeploymentConfig` resource. Often users, prefer to use `Deployment` as the main deployment resource, but still make use of Openshift specific resources like `Route`, `BuildConfig` etc.
  This feature is enabled by setting `quarkus.openshift.deployment-kind` to `Deployment`.
  
  