From 07a9454215173603871a444f61c20bfdc2abbd71 Mon Sep 17 00:00:00 2001
From: Benjamin Boudreau <boudreau.benjamin@gmail.com>
Date: Thu, 10 Oct 2019 16:11:37 -0400
Subject: [PATCH] doc: add configmap generator key example

---
 examples/configGeneration.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/examples/configGeneration.md b/examples/configGeneration.md
index 25d286c70..21adc3e0e 100644
--- a/examples/configGeneration.md
+++ b/examples/configGeneration.md
@@ -15,8 +15,10 @@ Kustomize provides two ways of adding ConfigMap in one `kustomization`, either b
 > configMapGenerator:
 > - name: a-configmap
 >   files:
+>     # configfile is used as key
 >     - configs/configfile
->     - configs/another_configfile
+>     # configkey is used as key
+>     - configkey=configs/another_configfile
 > ```
 
 The ConfigMaps declared as [resource] are treated the same way as other resources. Kustomize doesn't append any hash to the ConfigMap name. The ConfigMap declared from a ConfigMapGenerator is treated differently. A hash is appended to the name and any change in the ConfigMap will trigger a rolling update.