Merge pull request #1363 from thesteve0/patch-1

Clarifying the purpose and intended use of a ConfigMap
reviewable/pr1820/r3
devin-donnelly 2016-12-21 16:29:40 -08:00 committed by GitHub
commit 51d3c31300
1 changed files with 3 additions and 1 deletions

View File

@ -20,7 +20,9 @@ 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.
Let's look at a made-up example:
Note: ConfigMaps are not intended to act as a replacement for a properties file. ConfigMaps are intended to act as a reference to multiple properties files. You can think of them as way to represent something similar to the /etc directory, and the files within, on a Linux computer. One example of this model is creating Kubernetes Volumes from ConfigMaps, where each data item in the ConfigMap becomes a new file.
Consider the following example:
```yaml
kind: ConfigMap