whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Callouts and other small formatting (#5022)

Browse Source 
* Removing Extra Spaces

Issue 4602 | Configure Pods and Containers

* Update security-context.md

Adding callouts

* Update security-context.md

* Adding callout and fixing code block

* Removing extra space

* Adding callout

* Addling callouts

* Update assign-cpu-resource.md

* Adding callout

* Update configure-persistent-volume-storage.md

* Update configure-service-account.md

* Update quality-service-pod.md

* Update security-context.md
This commit is contained in:
Cody Clark
2017-08-17 16:19:24 -07:00
committed by Steve Perry
parent c5ad73c2d8
commit 7c4e01887b
9 changed files with 28 additions and 19 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/tasks/configure-pod-container/configmap.md
+2 -1
View File
@@ -223,7 +223,8 @@ metadata:
ConfigMaps allow you to decouple configuration artifacts from image content to keep containerized applications portable.
The ConfigMap API resource stores configuration data as key-value pairs. The data can be consumed in pods or provide the configurations for system components such as controllers. ConfigMap is similar to [Secrets](/docs/concepts/configuration/secret/), but provides a means of working with strings that don't contain sensitive information. Users and system components alike can store configuration data in ConfigMap.
Note: ConfigMaps should reference properties files, not replace them. Think of the ConfigMap as representing something similar to the Linux `/etc` directory and its contents. For example, if you create a [Kubernetes Volume](/docs/concepts/storage/volumes/) from a ConfigMap, each data item in the ConfigMap is represented by an individual file in the volume.
**Note:** ConfigMaps should reference properties files, not replace them. Think of the ConfigMap as representing something similar to the Linux `/etc` directory and its contents. For example, if you create a [Kubernetes Volume](/docs/concepts/storage/volumes/) from a ConfigMap, each data item in the ConfigMap is represented by an individual file in the volume.
{: .note}
The ConfigMap's `data` field contains the configuration data. As shown in the example below, this can be simple -- like individual properties defined using `--from-literal` -- or complex -- like configuration files or JSON blobs defined using `--from-file`.