Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
axel7083 opened this issue Nov 26, 2024 · 2 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@axel7083
Copy link
Contributor

axel7083 commented Nov 26, 2024

What would you like to be added?

Podman has a special format1 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

@axel7083 axel7083 added the kind/feature Categorizes issue or PR as related to a new feature. label Nov 26, 2024
@hangyan
Copy link
Contributor

hangyan commented Nov 30, 2024

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
Copy link

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

4 participants