anchor.diff:                fieldPath: metadata.annotations
     restartPolicy: Never
   ----
  +====
   
   . Create the pod from the `*_volume-pod.json_*` file:
  -
  ++
   ====
   ----
   $ oc create -f volume-pod.json
   ----
   ====
   
  -. Check the container's logs with:
  -
  +. Check the container's logs and verify the presence of the configured fields:
  ++
   ====
   ----
   $ oc logs -p dapi-volume-test-pod
  
positive.code:               fieldPath: metadata.namespace
    restartPolicy: Never
  ----
  
  . Create the pod from the `*_pod.json_*` file:
  
  ====
  ----
  $ oc create -f pod.json
  ----
  ====
  
  . Check the container's logs with:
  
  ====
  ----
  $ oc logs -p dapi-env-test-pod
  ----
  ====
  
  You should see `MY_POD_NAME` and `MY_POD_NAMESPACE` in the logs.
  
  == Consuming via volume plugin
  
  Another mechanism for consuming the downward API is the volume plug-in.  The downward API volume
  plug-in creates a volume with configured fields projected into files.  The `metadata` field of the
  `*VolumeSource*` API resource is used to configure this volume.  The plug-in supports the following
  fields:
  
  <1>  Pod name
  <2>  Pod namespace
  <3>  Pod annotations
  <4>  Pod labels
  
  Let's look at a small example of how the volume plug-in is configured:
  
  [source,yaml]
  ====
  ----
  spec:
    volumes:
  
negative.code:             fieldRef:
                fieldPath: metadata.labels <4>
  ----
  <1> The `*metadata*` field of the volume source configures the downward API
  volume.
  <2> The `*items*` field holds a list of fields to project into the volume.
  <3> The name of the file to project the field into.
  <4> The selector of the field to project.
  ====
  
  For example:
  
  . Create a `*_volume-pod.json_*` file:
  +
  ====
  [source,yaml]
  ----
  kind: Pod
  