From d59443b6fbea2717a228c8a013733006799ed00c Mon Sep 17 00:00:00 2001 From: Steven Pousty Date: Fri, 30 Sep 2016 14:44:18 -0700 Subject: [PATCH] Clarifying the purpose and intended use of a ConfigMap --- docs/user-guide/configmap/index.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/user-guide/configmap/index.md b/docs/user-guide/configmap/index.md index f37c83f4ac..e6d8686f00 100644 --- a/docs/user-guide/configmap/index.md +++ b/docs/user-guide/configmap/index.md @@ -19,6 +19,8 @@ or used to store configuration data for system components such as controllers. to [Secrets](/docs/user-guide/secrets/), but designed to more conveniently support working with strings that do not contain sensitive information. +Note: ConfigMaps are not intended to act as a replacement for a properties file. ConfigMaps are more intended to act a reference to multipe propertie files. You can think of them as way to represent something similar to the /etc directory and all it's files on a Linux computer. This model for ConfigMaps becomes especially apparent when looking at creating Volumes from ConfigMaps. Each data item in the ConfigMap becomes a new file. + Let's look at a made-up example: ```yaml