[Request]: Add --mount option to container k8s create

[janishorsts]

Feature or enhancement request details

Currently container k8s create does not support mounting host directories into the node container, unlike container create / container run.

Adding --mount support allows mounts to the cluster node (useful for sharing data, config or other files directly into the k8s node) same way as container create / container run.

Example:

container k8s create --name dev --mount type=virtiofs,source=/foo/bar,target=/data,readonly

Code of Conduct

• I agree to follow this project's Code of Conduct

[egernst]

What's the typical user story for this? I'm not sure that k8s create should really map 1:1 what you'd do for a general container -- the fact that a 'node' is run within a container image is almost an implementation detail for most folks.

I'm wondering if you'd be better suited using a custom node image?

[janishorsts]

To provide persistent storage for Persistent Volume Claims in k8s.

Currently, k8s is ephemeral: when deleting the k8s container, the volumes are gone. The --mount option ensures these volumes persist.

Without volume persistence, "container k8s" has very narrow use cases on developer machines.

[shoce]

I double the request. Having --volume/--mount would allow me to have hostPath volumes on my macbook.

[shoce]

@egernst please take a look at my PR #2283 - it adds both --volume and --mount options in a clean way

[jlehman9]

What's the typical user story for this? I'm not sure that k8s create should really map 1:1 what you'd do for a general container -- the fact that a 'node' is run within a container image is almost an implementation detail for most folks.

I can't use container on it's own right now due to this since my team's main Helm Chart requires a postgresql container that uses volumes like this. The kiac handles this for me so I've been playing around with that on top of container, but having it native would be great so I wouldn't need a 3rd party tool. Excited for this PR.