anchor.diff:  ====
   
   ----
  -LABEL openshift.io/wants   mongodb,redis
  +LABEL io.openshift.wants   mongodb,redis
   ----
   ====
   
  -|`*k8s.io/description*`
  +|`*io.k8s.description*`
   |This label can be used to give the Docker image consumers more detailed
   information about the service or functionality this image provides. The UI can
   then use this description together with the Docker image name to provide more
  
positive.code: ====
  
  ----
  LABEL openshift.io/non-scalable     true
  ----
  ====
  
  |`*openshift.io/min-memory*` and `*openshift.io/min-cpu*`
  |This label suggests how much resources the Docker image might need in order to
  work properly. The UI might warn the user that deploying this Docker image may
  exceed their user quota.  The values must be compatible with
  
negative.code: 
  The label names should typically be namespaced. The namespace should be set
  accordingly to reflect the project that is going to pick up the labels and use
  them. For OpenShift the namespace should be set to *_io.openshift_* and for
  Kubernetes the namespace is *_io.k8s_*.
  
  See the https://docs.docker.com/userguide/labels-custom-metadata[Docker custom
  metadata] documentation for details about the format.
  
  .Supported Metadata
  [cols="3a,8a",options="header"]
  