Description

Feature Overview

This would add --volumes-from support to podman kube support. This allows for a data management flow with an image being used to create but never start a container that is bind mounted into another container via --volumes-from.

Related Issue: https://issues.redhat.com/browse/RHEL-24715

PR with upstream Fix: https://github.com/containers/podman/pull/22410

Release Note: A list of images to automatically mount as volumes can now be specified in Kubernetes YAML via the "io.podman.annotations.kube.image.automount/$ctrname" annotation. Image-based mounts using `podman run --mount type=image,...` now support a new option, `subpath`, to mount only part of the image into the container.

Man Page Addition:

`Automounting Volumes`

An image can be automatically mounted into a container if the annotation `io.podman.annotations.kube.image.automount/$ctrname` is given. The following rules apply:

• The image must already exist locally.

• The image must have at least 1 volume directive.
• The path given by the volume directive will be mounted from the image into the container. For example, an image with a volume at `/test/test_dir` will have `/test/test_dir` in the image mounted to `/test/test_dir` in the container.
• Multiple images can be specified. If multiple images have a volume at a specific path, the last image specified trumps.
• The images are always mounted read-only.
• Images to mount are defined in the annotation "io.podman.annotations.kube.image.automount/$ctrname" as a semicolon-separated list. They are mounted into a single container in the pod, not the whole pod. The annotation can be specified for additional containers if additional mounts are required.

This has been completed upstream.

Goals

Partner request.