anchor.diff:  
   The above commands should result in the plain text values, the decoding is done for you.
   
  -*Using Environment Variables*, deploy the pod:
  +==== Using Environment Variables
  +
  +Deploy the pod:
   
       kubectl apply -f ./templates/pod-secret-env.yaml
   
  
positive.code: 
  The above commands illustrate how to see the secret values via environment variables
  
  == Conclusion
  
  In this post we demonstrated how to leverage configmaps and secrets in your pods.
  
negative.code: :linkcss:
  :imagesdir: ../images
  
  = Kubernetes ConfigMap and Secrets
  :toc:
  
  Kubernetes has resource types that allows to decouple application code from configuration. It makes the applications to be more portable.
  
  ConfigMap is just a set of key-value pairs. It allow you to decouple configuration artifacts from image content. Secrets allows separating sensitive information such as credentials and keys from an application. ConfigMap is similar to Secrets, but provides a means of working with strings that don’t contain sensitive information.
  
  This section will explain how to use ConfigMap and Secrets.
  
  == ConfigMap
  
  We will illiustrate how to pass this information to a Redis pod, by passing configuration information with Configmap.
  
  === Create the ConfigMap object
  
      kubectl apply -f ./templates/config-map.yaml
  
  === Deploy a Redis pod
  
  Deploy a Redis pod that maps the Configmap to the volume where the configuration resides:
  
      kubectl apply -f ./templates/redis-pod.yaml
  
  === Validate Redis cluster
  
  Validate that your redis cluster picked up the appropriate configuration:
  
      kubectl exec --it redis redis-cli
      CONFIG GET maxmemory
  