[idea] kompose could output podman kube play format for compose with build option

[axel7083]

What would you like to be added?

Podman has a special format¹ to be able to build a container while defining a pod yaml, here is an example

With the following folder structure

|- mykubefiles
    |- myplayfile.yaml
    |- foobar
         |- Containerfile

myplayfile.yaml

apiVersion: v1
kind: Pod
metadata:
...
spec:
  containers:
  - name: container
    image: foobar

if you run (on linux)

$: podman kube play --build myplayfile.yaml

This will build the mykubefiles/foobar/Containerfile container with the foobar context and start a pod with the image just built, and would allow to directly use podman to start the application.

Why is this needed?

This would be interesting to have the resources yaml definition where we can remove the compose file, since we have an equivalent (in some maner, the build do not have much option (yet?) )

Footnotes

1. https://docs.podman.io/en/stable/markdown/podman-kube-play.1.html ↩

[hangyan]

sorry i didn't see the connection. kompose is aimied to generate k8s yaml based on docker compose. Can you explain more?

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale