anchor.diff:  
   . Create a ConfigMap:
   
  -  kubectl create configmap hello-count --from-literal=COUNT=2
  +  $ kubectl create configmap hello-count --from-literal=COUNT=2
  +  configmap "hello-count" created
   
   . Get more details about this ConfigMap:
   
  
positive.code: 
  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
  ```
  
  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
  ```
  
  You should see the same values that were specified in `./templates/redis-configmap.yaml` outputted in the above commands.
  
  
negative.code: 
  Create a ConfigMap:
  
      $ kubectl apply -f ./templates/redis-configmap.yaml
      configmap "redis-config" created
  
  `redis-configmap.yaml` is a standard resource configuration file. It defines the configuration information as:
  
      data:
        redis-config: |
          maxmemory=2mb
          maxmemory-policy=allkeys-lru
  
  The configuration data is stored in the main key `data`. `redis-config` is an attribute inside this key where the configuration information for the Redis pod is defined as key-value pairs.
  
  Get the list of ConfigMaps:
  
      $ kubectl get configmap
      NAME           DATA      AGE
      redis-config   1         14s
  
  Get more details about the created ConfigMap:
  
  