anchor.diff:  ----
   ====
   
  -[[real-world-example-configuring-redis]]
  -## Real World Example: Configuring Redis
  -
  -Let's take a look at a real-world example: configuring redis using ConfigMap.  Say we want to inject
  -redis with the recommendation configuration for using redis as a cache.  The redis config file
  -should contain:
  +[[configmaps-example-configuring-redis]]
  +== Example: Configuring Redis
  +
  +For a real-world example, you can configure Redis using a `*ConfigMap*`. To
  +inject Redis with the recommended configuration for using Redis as a cache, the
  +Redis configuration file should contain the following:
   
   ====
   ----
  
positive.code: ----
  ====
  
  We can consume the keys of this ConfigMap in a pod like so:
  
  ====
  [source,yaml]
  
negative.code: 
  toc::[]
  
  == Overview
  
  Many applications require configuration using some combination of configuration
  files, command line arguments, and environment variables. These configuration
  artifacts should be decoupled from image content in order to keep containerized
  applications portable.
  
  The `*ConfigMap*` object provides mechanisms to inject containers with
  configuration data while keeping containers agnostic of {product-title}. A
  `*ConfigMap*` can be used to store fine-grained information like individual
  properties or coarse-grained information like entire configuration files or JSON
  blobs.
  
  The `*ConfigMap*` API object holds key-value pairs of configuration data that
  can be consumed in pods or used to store configuration data for system
  components such as controllers. `*ConfigMap*` is similar to
  link:../dev_guide/secrets.html[secrets], but designed to more conveniently
  support working with strings that do not contain sensitive information.
  
  For example:
  
  .ConfigMap Object Definition
  ====
  [source,yaml]
  ----
  