creating kompose extension

[axel7083]

Is your feature request related to a problem? Please describe

The Generate kube action on a COMPOSE containerGroup creates a pod with many containers. Which is working but not really common behaviour when porting compose file to Kubernetes.

Example

Will generate

apiVersion: v1
kind: Pod
metadata:
...
spec:
  containers:
  - image: registry.k8s.io/redis:e2e
    ...
  - image: registry.k8s.io/redis-slave:v2
    ...
  - image: registry.k8s.io/guestbook:v3
    ...

Describe the solution you'd like

The Kompose project could be used in an extension to enhance the files generated. If #3959 is merged, an extension could add a menu actions to generate a more details output.

Describe alternatives you've considered

No response

Additional context

No response

[benoitf]

@axel7083 do you need a Deployment object when using podman generate ?

We filed a RFE in upstream podman to be able to generate a Deployment (and not only a Pod)

containers/podman#17712

containers/podman#17950

[axel7083]

@axel7083 do you need a Deployment object when using podman generate ?

We filed a RFE in upstream podman to be able to generate a Deployment (and not only a Pod)

containers/podman#17712

containers/podman#17950

Kompose is going further, generating individual Deployment¹ files for each services in the Docker-compose file.
It also creates Services², Configmaps³ etc.

Footnotes

1. Deployment ↩

2. Services ↩

3. ConfigMaps ↩

[github-actions]

This issue has been automatically marked as stale because it has not had activity in the last 6 months. It will be closed in 30 days if no further activity occurs. Please feel free to leave a comment if you believe the issue is still relevant. Thank you for your contributions!

[github-actions]

This issue has been automatically closed because it has not had any further activity in the last 30 days. Thank you for your contributions!