Skip to content

Commit

Permalink
Merge branch 'master' of github.com:xinity/devopsg-security
Browse files Browse the repository at this point in the history
  • Loading branch information
xinity committed Mar 10, 2019
2 parents f77339b + 5d24012 commit 63865ed
Showing 1 changed file with 5 additions and 5 deletions.
10 changes: 5 additions & 5 deletions secrets/README.md → secrets/README.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ First encode the secrets you want to apply, for this example we will use the use
echo -n "admin" | base64
echo -n "password" | base64

Both of these values are already written in the file `./templates/secret.yaml`. The configuration looks like:
The configuration looks like:

```
apiVersion: v1
Expand All @@ -24,7 +24,7 @@ data:

You can now insert this secret in the Kubernetes cluster with the following command:

kubectl apply -f ./templates/secret.yaml
kubectl apply -f ./secret.yaml

The list of created secrets can be seen as:

Expand Down Expand Up @@ -56,7 +56,7 @@ Once again, the values of the secret are not shown.

Deploy the pod:

kubectl apply -f ./templates/pod-secret-volume.yaml
kubectl apply -f ./pod-secret-volume.yaml

The pod configuration file looks like:

Expand Down Expand Up @@ -88,13 +88,13 @@ The above commands should result in the plain text values, the decoding is done

Delete the pod:

kubectl delete -f ./templates/pod-secret-volume.yaml
kubectl delete -f ./pod-secret-volume.yaml

=== Consume as pod environment variables

Deploy the pod:

kubectl apply -f ./templates/pod-secret-env.yaml
kubectl apply -f ./pod-secret-env.yaml

The pod configuration file looks like:

Expand Down

0 comments on commit 63865ed

Please sign in to comment.