From 1e9bfeb1f8edcca3f6e15294772da76c6b2c6253 Mon Sep 17 00:00:00 2001 From: flouthoc Date: Mon, 3 Mar 2025 08:53:02 -0800 Subject: [PATCH] docs,kube: add configMap as supported volume option Closes: https://github.com/containers/podman/issues/25436 [NO NEW TESTS NEEDED] [NO TESTS NEEDED] Signed-off-by: flouthoc --- docs/source/markdown/podman-kube-play.1.md.in | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/source/markdown/podman-kube-play.1.md.in b/docs/source/markdown/podman-kube-play.1.md.in index 729627f5f2..5ed9a4b766 100644 --- a/docs/source/markdown/podman-kube-play.1.md.in +++ b/docs/source/markdown/podman-kube-play.1.md.in @@ -28,11 +28,12 @@ Currently, the supported Kubernetes kinds are: `Kubernetes Pods or Deployments` -Only four volume types are supported by kube play, the *hostPath*, *emptyDir*, *persistentVolumeClaim*, and *image* volume types. +Only five volume types are supported by kube play, the *hostPath*, *emptyDir*, *configMap*, *persistentVolumeClaim*, and *image* volume types. - When using the *hostPath* volume type, only the *default (empty)*, *DirectoryOrCreate*, *Directory*, *FileOrCreate*, *File*, *Socket*, *CharDevice* and *BlockDevice* subtypes are supported. Podman interprets the value of *hostPath* *path* as a file path when it contains at least one forward slash, otherwise Podman treats the value as the name of a named volume. - When using a *persistentVolumeClaim*, the value for *claimName* is the name for the Podman named volume. - When using an *emptyDir* volume, Podman creates an anonymous volume that is attached the containers running inside the pod and is deleted once the pod is removed. +- When using an *configMap* volume, Podman creates an anonymous volume that is attached the containers running inside the pod and is deleted once the pod is removed. - When using an *image* volume, Podman creates a read-only image volume with an empty subpath (the whole image is mounted). The image must already exist locally. It is supported in rootful mode only. Note: The default restart policy for containers is `always`. You can change the default by setting the `restartPolicy` field in the spec.