anchor.diff:  ----
   ====
   
  -. Check the container's logs:
  +. Check the container's logs for the `*MY_POD_NAME*` and `*MY_POD_NAMESPACE*`
  +values:
   +
   ====
   ----
   $ oc logs -p dapi-env-test-pod
   ----
   ====
  -+
  -You should see `MY_POD_NAME` and `MY_POD_NAMESPACE` in the logs.
  -
  -[[dapi-using-volume-plugin]]
  -== Using the Volume Plug-in
  +
  +[[dapi-values-using-volume-plugin]]
  +=== Using the Volume Plug-in
   
   Another mechanism for consuming the downward API is using a volume plug-in. The
   downward API volume plug-in creates a volume with configured fields projected
  
positive.code: 
  == Overview
  
  It is common for containers to consume information about API objects. The
  downward API is a mechanism that allows containers to do this without coupling
  to {product-title}. Containers can consume information from the downward API
  xref:dapi-using-environment-variables[using environment variables] or a
  xref:dapi-using-volume-plugin[volume plug-in].
  
  == Selecting Fields
  
  
negative.code: - Pod name
  - Pod namespace
  
  . Create a `*_pod.json_*` file:
  +
  ====
  