github/container.training
1
0
Fork 0
mirror of https://github.com/jpetazzo/container.training.git synced 2026-07-16 03:19:18 +00:00
Code Issues Packages Projects Releases Wiki Activity

🐞 Fix secret names in exercise

Browse Source
This commit is contained in:
Jérôme Petazzoni
2021-11-12 08:31:07 +01:00
parent 23eb0ed771
commit 8f03ce674a
1 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
slides/exercises/sealed-secrets-details.md
View File

@@ -24,9 +24,9 @@ We will call them "dev cluster" and "prod cluster".
- Our application needs two secrets:
- `logging_api_token` (not too sensitive; same in dev and prod)
- a *logging API token* (not too sensitive; same in dev and prod)
- `database_password` (sensitive; different in dev and prod)
- a *database password* (sensitive; different in dev and prod)
- Secrets can be exposed as env vars, or mounted in volumes
@@ -42,7 +42,7 @@ We will call them "dev cluster" and "prod cluster".
- On the dev cluster, create a Namespace called `dev`
- Create the two secrets, `logging_api_token` and `database_password`
- Create the two secrets, `logging-api-token` and `database-password`
(the content doesn't matter; put a random string of your choice)
@@ -110,8 +110,8 @@ We want Alice to be able to:
- deploy the whole application in the `prod` namespace
- access the `logging_api_token` secret
- access the *logging API token* secret
- but *not* the `database_password` secret
- but *not* the *database password* secret
- view the logs of the app