anchor.diff:  
   Check logs from the pod to verify that Redis has started:
   
  -```
  -$ kubectl logs redis-pod
  -                _._                                                  
  -           _.-``__ ''-._                                             
  -      _.-``    `.  `_.  ''-._           Redis 2.8.19 (00000000/0) 64 bit
  -  .-`` .-```.  ```\/    _.,_ ''-._                                   
  - (    '      ,       .-`  | `,    )     Running in stand alone mode
  - |`-._`-...-` __...-.``-._|'` _.-'|     Port: 6379
  - |    `-._   `._    /     _.-'    |     PID: 6
  -  `-._    `-._  `-./  _.-'    _.-'                                   
  - |`-._`-._    `-.__.-'    _.-'_.-'|                                  
  - |    `-._`-._        _.-'_.-'    |           http://redis.io        
  -  `-._    `-._`-.__.-'_.-'    _.-'                                   
  - |`-._`-._    `-.__.-'    _.-'_.-'|                                  
  - |    `-._`-._        _.-'_.-'    |                                  
  -  `-._    `-._`-.__.-'_.-'    _.-'                                   
  -      `-._    `-.__.-'    _.-'                                       
  -          `-._        _.-'                                           
  -              `-.__.-'                                               
  -
  -[6] 22 Oct 18:39:45.386 # Server started, Redis version 2.8.19
  -[6] 22 Oct 18:39:45.386 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command 'echo never > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled.
  -[6] 22 Oct 18:39:45.386 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
  -[6] 22 Oct 18:39:45.386 * The server is now ready to accept connections on port 6379
  -```
  +  $ kubectl logs redis-pod
  +                  _._                                                  
  +             _.-``__ ''-._                                             
  +        _.-``    `.  `_.  ''-._           Redis 2.8.19 (00000000/0) 64 bit
  +    .-`` .-```.  ```\/    _.,_ ''-._                                   
  +   (    '      ,       .-`  | `,    )     Running in stand alone mode
  +   |`-._`-...-` __...-.``-._|'` _.-'|     Port: 6379
  +   |    `-._   `._    /     _.-'    |     PID: 6
  +    `-._    `-._  `-./  _.-'    _.-'                                   
  +   |`-._`-._    `-.__.-'    _.-'_.-'|                                  
  +   |    `-._`-._        _.-'_.-'    |           http://redis.io        
  +    `-._    `-._`-.__.-'_.-'    _.-'                                   
  +   |`-._`-._    `-.__.-'    _.-'_.-'|                                  
  +   |    `-._`-._        _.-'_.-'    |                                  
  +    `-._    `-._`-.__.-'_.-'    _.-'                                   
  +        `-._    `-.__.-'    _.-'                                       
  +            `-._        _.-'                                           
  +                `-.__.-'                                               
  +
  +  [6] 22 Oct 18:39:45.386 # Server started, Redis version 2.8.19
  +  [6] 22 Oct 18:39:45.386 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command 'echo never > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled.
  +  [6] 22 Oct 18:39:45.386 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
  +  [6] 22 Oct 18:39:45.386 * The server is now ready to accept connections on port 6379
   
   Validate that your redis cluster picked up the appropriate configuration:
   
  -```
  -$ kubectl exec redis-pod -it redis-cli
  -127.0.0.1:6379> CONFIG GET maxmemory
  -1) "maxmemory"
  -2) "2097152"
  -127.0.0.1:6379> CONFIG GET maxmemory-policy
  -1) "maxmemory-policy"
  -2) "allkeys-lru"
  -127.0.0.1:6379> quit
  -```
  +    $ kubectl exec redis-pod -it redis-cli
  +    127.0.0.1:6379> CONFIG GET maxmemory
  +    1) "maxmemory"
  +    2) "2097152"
  +    127.0.0.1:6379> CONFIG GET maxmemory-policy
  +    1) "maxmemory-policy"
  +    2) "allkeys-lru"
  +    127.0.0.1:6379> quit
   
   You should see the same values that were specified in `./templates/redis-configmap.yaml` outputted in the above commands.
   
  
positive.code: 
  We created a ConfigMap using a resource configuration file. Other ways to create ConfigMap are listed below:
  
  . `kubectl create configmap --from-literal=<key>:<value>`. Multiple `--from-literal=<key>:<value>` options can be used to define different key/value pairs. For example:
  +
  ```
  kubectl create configmap redis-config --from-literal=maxmemory=2mb --from-literal=maxmemory-policy=allkeys-lru
  ```
  +
  More details about the ConfigMap can be obtained as:
  +
  ```
  $ kubectl get configmap/redis-config -o yaml
  apiVersion: v1
  data:
    maxmemory: 2mb
    maxmemory-policy: allkeys-lru
  kind: ConfigMap
  metadata:
    creationTimestamp: 2017-10-22T15:29:31Z
    name: redis-config
    namespace: default
    resourceVersion: "287452"
    selfLink: /api/v1/namespaces/default/configmaps/redis-config
    uid: cccf20b7-b73d-11e7-8c3f-06329c8974cc
  ```
  +
  . `kubectl create configmap redis-config --from-file=<properties file>` where `<properties file>` is a property file with key/value pairs. For example, `templates/redis-config` looks like:
  +
  ```
  maxmemory 2mb
  maxmemory-policy allkeys-lru
  ```
  +
  And now ConfigMap can be created as:
  +
  ```
  kubectl create configmap redis-config --from-file=templates/redis-config
  ```
  +
  More details about the ConfigMap can be obtained as:
  +
  ```
  $ kubectl get configmap/redis-config -o yaml
  apiVersion: v1
  data:
    redis-config: |
      maxmemory=2mb
      maxmemory-policy=allkeys-lru
  kind: ConfigMap
  metadata:
    creationTimestamp: 2017-10-22T15:56:08Z
    name: redis-config
    namespace: default
    resourceVersion: "289533"
    selfLink: /api/v1/namespaces/default/configmaps/redis-config
    uid: 84901162-b741-11e7-8c3f-06329c8974cc
  ```
  +
  The filename becomes a key stored in the data section of the ConfigMap. The file contents become the key’s value.
  
  
negative.code: 
  Let's use `redis-config` ConfigMap to create our `redis.conf` configuration file in the pod `redis-pod`. It maps the ConfigMap to the volume where the configuration resides:
  
      $ kubectl apply -f ./templates/redis-pod.yaml
      pod "redis-pod" created
  
  Wait for the pod to run:
  
  