anchor.diff:  
   At the end of this section, you'll have created a ConfigMap `redis-config`.
   
  -=== Using ConfigMap in a Pod volume
  +=== Consume in a pod volume
   
   A ConfigMap must be created before referencing it in a Pod specification (unless you mark the ConfigMap as "`optional`"). If you reference a ConfigMap that doesn’t exist would , the Pod won’t start.
   
  
positive.code: . Wrap the pod in a Deployment
  . Terminate the pod, Deployment will restart the pod and pick up new configuration
  
  === Using ConfigMap data as Pod environment variables
  
  The data from ConfigMap can be used to initialize environment variables in a pod. We'll use `arungupta/print-hello` image to print "`Hello World`" on the console. The number of times this message is printed is defined by an environment variable `COUNT`. This value of this variable is defined in the ConfigMap.
  
  
negative.code: 
  The above commands should result in the plain text values, the decoding is done for you.
  
  Delete the pod:
  
      kubectl delete -f ./templates/pod-secret-volume.yaml
  
  === Consume as environment variables
  
  Deploy the pod:
  
      kubectl apply -f ./templates/pod-secret-env.yaml
  
  The pod configuration file looks like:
  
      apiVersion: v1
      kind: Pod
      metadata:
        name: pod-secret-env
      spec:
        containers:
        - name: pod-secret-env
          image: redis
          env:
            - name: SECRET_USERNAME
              valueFrom:
                secretKeyRef:
                  name: mysecret
                  key: username
            - name: SECRET_PASSWORD
              valueFrom:
                secretKeyRef:
                  name: mysecret
                  key: password
        restartPolicy: Never
  
  Open a shell to the pod to see the secrets:
  
      kubectl exec -it pod-secret-env /bin/bash
      echo $SECRET_USERNAME
      echo $SECRET_PASSWORD
  
  