summaryrefslogtreecommitdiff
path: root/docs/source/markdown/podman-play-kube.1.md
diff options
context:
space:
mode:
Diffstat (limited to 'docs/source/markdown/podman-play-kube.1.md')
-rw-r--r--docs/source/markdown/podman-play-kube.1.md13
1 files changed, 6 insertions, 7 deletions
diff --git a/docs/source/markdown/podman-play-kube.1.md b/docs/source/markdown/podman-play-kube.1.md
index f85ea9046..389affc3a 100644
--- a/docs/source/markdown/podman-play-kube.1.md
+++ b/docs/source/markdown/podman-play-kube.1.md
@@ -72,9 +72,11 @@ disable builds.
`Kubernetes ConfigMap`
-Kubernetes ConfigMap can be referred as a source of environment variables in Pods or Deployments.
+Kubernetes ConfigMap can be referred as a source of environment variables or volumes in Pods or Deployments.
+ConfigMaps aren't a standalone object in Podman; instead, when a container uses a ConfigMap, Podman will create environment variables or volumes as needed.
+
+For example, the following YAML document defines a ConfigMap and then uses it in a Pod:
-For example ConfigMap defined in following YAML:
```
apiVersion: v1
kind: ConfigMap
@@ -82,14 +84,11 @@ metadata:
name: foo
data:
FOO: bar
-```
-
-can be referred in a Pod in following way:
-```
+---
apiVersion: v1
kind: Pod
metadata:
-...
+ name: foobar
spec:
containers:
- command: