From 3fee166ee8a62e7accb2d55fd0060161d7845b4a Mon Sep 17 00:00:00 2001
From: Benjamin Baron <2346055+benjbaron@users.noreply.github.com>
Date: Thu, 23 May 2019 10:17:45 +0200
Subject: [PATCH] Add how to look up the secrets in both cases

---
 10-secrets/README.md | 21 +++++++++++++++++++++
 1 file changed, 21 insertions(+)

diff --git a/10-secrets/README.md b/10-secrets/README.md
index 688a66a..07da13e 100644
--- a/10-secrets/README.md
+++ b/10-secrets/README.md
@@ -24,6 +24,8 @@ secret "mysecret" created
 
 You can reference a secret from a pod, either per env variable or mounting a volume containing a secret.
 
+## Reference the secret by mounting it as a volume
+
 Here we mount the secret `mysecret` to the path `/etc/foo` inside the pod:
 
 ```yml
@@ -45,6 +47,16 @@ spec:
       secretName: mysecret
 ```
 
+You can look up the secrets in the pod by connecting to the pod:
+```
+$ kubectl exec -ti redis-with-volume-secrets /bin/bash
+root@redis-with-volume-secrets:/data# cd /etc/foo/
+root@redis-with-volume-secrets:/etc/foo# ls
+password  username
+```
+
+## Reference the secret by using environmental variables
+
 Here we bind the value `username` from the secret `mysecret` to the env variable `SECRET_USERNAME`,
 `password` from the secret `mysecret` to the env variable `SECRET_PASSWORD`:
 
@@ -70,6 +82,15 @@ spec:
             key: password
 ```
 
+You can look up the secrets in the pod by connecting to the pod:
+```
+$ kubectl exec -ti redis-with-env-secrets /bin/bash
+root@redis-with-env-secrets:/data# echo $SECRET_USERNAME
+admin
+root@redis-with-env-secrets:/data# echo $SECRET_PASSWORD
+1f2d1e2e67df
+```
+
 Careful, if you change a secret after starting the pods, it won't update the pods. So you need to restart them.
 
 ## Clean up