Add infra-name annotations to kube gen/play

Add io.podman.annotations.infra.name annotation to kube play so
users can set the name of the infra container created.
When a pod is created with --infra-name set, the generated
kube yaml will have an infraName annotation set that will
be used when playing the generated yaml with podman.

Signed-off-by: Urvashi Mohnani <umohnani@redhat.com>
This commit is contained in:
Urvashi Mohnani
2023-08-03 10:07:09 -04:00
parent f29986178e
commit 52ed7fce2a
8 changed files with 141 additions and 3 deletions

View File

@ -28,6 +28,8 @@ Once completed, the correct permissions are in place to access the volume when t
Note that the generated Kubernetes YAML file can be used to re-run the deployment via podman-play-kube(1).
Note that if the pod being generated was created with the **--infra-name** flag set, then the generated kube yaml will have the **io.podman.annotations.infra.name** set where the value is the name of the infra container set by the user.
## OPTIONS
#### **--filename**, **-f**=*filename*

View File

@ -45,6 +45,8 @@ Note: The command `podman play kube` is an alias of `podman kube play`, and perf
Note: The command `podman kube down` can be used to stop and remove pods or containers based on the same Kubernetes YAML used
by `podman kube play` to create them.
Note: To customize the name of the infra container created during `podman kube play`, use the **io.podman.annotations.infra.name** annotation in the pod definition. This annotation is automatically set when generating a kube yaml from a pod that was created with the `--infra-name` flag set.
`Kubernetes PersistentVolumeClaims`
A Kubernetes PersistentVolumeClaim represents a Podman named volume. Only the PersistentVolumeClaim name is required by Podman to create a volume. Kubernetes annotations can be used to make use of the available options for Podman volumes.