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.md35
1 files changed, 35 insertions, 0 deletions
diff --git a/docs/source/markdown/podman-play-kube.1.md b/docs/source/markdown/podman-play-kube.1.md
index 2438f7ad8..2a511f4bd 100644
--- a/docs/source/markdown/podman-play-kube.1.md
+++ b/docs/source/markdown/podman-play-kube.1.md
@@ -16,6 +16,7 @@ Currently, the supported Kubernetes kinds are:
- Pod
- Deployment
- PersistentVolumeClaim
+- ConfigMap
`Kubernetes Pods or Deployments`
@@ -68,6 +69,40 @@ like:
The build will consider `foobar` to be the context directory for the build. If there is an image in local storage
called `foobar`, the image will not be built unless the `--build` flag is used.
+`Kubernetes ConfigMap`
+
+Kubernetes ConfigMap can be referred as a source of environment variables in Pods or Deployments.
+
+For example ConfigMap defined in following YAML:
+```
+apiVersion: v1
+kind: ConfigMap
+metadata:
+ name: foo
+data:
+ FOO: bar
+```
+
+can be referred in a Pod in following way:
+```
+apiVersion: v1
+kind: Pod
+metadata:
+...
+spec:
+ containers:
+ - command:
+ - top
+ name: container-1
+ image: foobar
+ envFrom:
+ - configMapRef:
+ name: foo
+ optional: false
+```
+
+and as a result environment variable `FOO` will be set to `bar` for container `container-1`.
+
## OPTIONS
#### **--authfile**=*path*