Skip to content

Commit 51d3c31

Browse files
Merge pull request #1363 from thesteve0/patch-1
Clarifying the purpose and intended use of a ConfigMap
2 parents ce5a76e + 1d3f64a commit 51d3c31

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

docs/user-guide/configmap/index.md

+3-1
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,9 @@ or used to store configuration data for system components such as controllers.
2020
to [Secrets](/docs/user-guide/secrets/), but designed to more conveniently support working with strings that do not
2121
contain sensitive information.
2222

23-
Let's look at a made-up example:
23+
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.
24+
25+
Consider the following example:
2426

2527
```yaml
2628
kind: ConfigMap

0 commit comments

Comments
 (0)