anchor.diff:  
   You should see the same values that were specified in the ./templates/config-map.yaml outputted in the above commands.
   
  -=== Secrets
  +== Secrets
   
  -In this section we will demonstrate how to place secrets into the k8s cluster and then show multiple ways of retrieving those secretes from within pods.
  +In this section we will demonstrate how to place secrets into the Kubernetes cluster and then show multiple ways of retrieving those secretes from within pods.
  +
  +=== Create secrets
   
   First encode the secrets you want to apply, for this example we will use the username `admin` and the password `password`
   
  
positive.code: :linkcss:
  :imagesdir: ../images
  
  = Kubernetes Configmap and Secrets
  :toc:
  
  == Kubernetes - Configmap and Secrets
  
  Kubernetes as a resource type of Configmap used as a way to abstract pods away from their configuration helping keep the applications more portable.
  
  There is also a secrets object which allows you to pass sensitive data to your applications.
  
  Here will will illiustrate how to pass this information to a redis pod, by passing configuration information with Configmap.
  
  Next
  
  === Create the Configmap object
  
      kubectl apply -f ./templates/config-map.yaml
  
  === Deploy a redis pod that maps the Configmap to the volume where the configuration resides:
  
      kubectl apply -f ./templates/redis-pod.yaml
  
  === Validate that your redis cluster picked up the appropriate configuration:
  
      kubectl exec --it redis redis-cli
      CONFIG GET maxmemory
  
negative.code: 
      kubectl apply -f ./templates/secret.yaml
  
  === Consume secrets
  
  Here we will demonstrate two ways to consume secrets from within pods.
  
  ==== Using volumes
  
  Deploy the pod:
  
      kubectl apply -f ./templates/pod-secret-volume.yaml
  
  