opensource/podman
1
0
Fork 0
mirror of https://github.com/containers/podman.git synced 2025-10-17 11:14:40 +08:00
Code Issues Packages Projects Releases Wiki Activity

Document kube-play CDI support

Browse Source 
Follow up to ec6b0355bf9c9b90b774707b6adc49a743cbebd4

Signed-off-by: Robert Günzler <r@gnzler.io>
This commit is contained in:
Robert Günzler
2025-01-16 15:35:37 +01:00
parent 31dd624951
commit d4f4cf0988
1 changed files with 17 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
docs/source/markdown/podman-kube-play.1.md.in
View File

@ -97,6 +97,23 @@ The build considers `foobar` to be the context directory for the build. If there
called `foobar`, the image is not built unless the `--build` flag is used. Use `--build=false` to completely called `foobar`, the image is not built unless the `--build` flag is used. Use `--build=false` to completely
disable builds. disable builds.
Kube play supports CDI (Container Device Interface) device selectors to share
host devices (e.g. GPUs) with containers. The configuration format follows
Kubernetes extended resource management:
```
apiVersion: v1
kind: Pod
spec:
containers:
- name: container
resources:
limits:
nvidia.com/gpu=all: 1
```
To enable sharing host devices, analogous to using the `--device` flag Podman
kube supports a custom CDI selector: `podman.io/device=<host device path>`.
`Kubernetes ConfigMap` `Kubernetes ConfigMap`
Kubernetes ConfigMap can be referred as a source of environment variables or volumes in Pods or Deployments. Kubernetes ConfigMap can be referred as a source of environment variables or volumes in Pods or Deployments.