From 8f03ce674a58be065b4cdbe527e36c8ea87de668 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?J=C3=A9r=C3=B4me=20Petazzoni?= Date: Fri, 12 Nov 2021 08:31:07 +0100 Subject: [PATCH] =?UTF-8?q?=F0=9F=90=9E=20Fix=20secret=20names=20in=20exer?= =?UTF-8?q?cise?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- slides/exercises/sealed-secrets-details.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/slides/exercises/sealed-secrets-details.md b/slides/exercises/sealed-secrets-details.md index 1c931191..4ba7b2f1 100644 --- a/slides/exercises/sealed-secrets-details.md +++ b/slides/exercises/sealed-secrets-details.md @@ -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