From eb0fbf236bf8ccf619237cbecec1f08c602519b1 Mon Sep 17 00:00:00 2001 From: Brett Nekolny Date: Wed, 12 May 2021 17:29:17 -0600 Subject: [PATCH] Add envs example for secretGenerator. --- .../managing-secret-using-kustomize.md | 14 +++++++++++++- 1 file changed, 13 insertions(+), 1 deletion(-) diff --git a/content/en/docs/tasks/configmap-secret/managing-secret-using-kustomize.md b/content/en/docs/tasks/configmap-secret/managing-secret-using-kustomize.md index fb257a6026..4e78a4c5f0 100644 --- a/content/en/docs/tasks/configmap-secret/managing-secret-using-kustomize.md +++ b/content/en/docs/tasks/configmap-secret/managing-secret-using-kustomize.md @@ -48,7 +48,19 @@ secretGenerator: - password=1f2d1e2e67df ``` -Note that in both cases, you don't need to base64 encode the values. +You can also define the `secretGenerator` in the `kustomization.yaml` +file by providing `.env` files. +For example, the following `kustomization.yaml` file pulls in data from +`.env.secret` file: + +```yaml +secretGenerator: +- name: db-user-pass + envs: + - .env.secret +``` + +Note that in all cases, you don't need to base64 encode the values. ## Create the Secret