Open cdrage opened 11 months ago
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!
This issue has been automatically closed because it has not had any further activity in the last 30 days. Thank you for your contributions!
Still valid
Is your enhancement related to a problem? Please describe
I ran into another issue with converting to Kubernetes, to be honest the conversion from the group of compose containers to Kubernetes is done.. poorly with regards to services and being able to access them through the namespace.
For example, if we were to deploy only ONE container, it would be converted correctly. But say if we were to deploy multiple containers where they would be able to access each-other via services? For example, within a
frontend
container, you can pingredis-master
, it will not work due to the way we are converting services.When converting this example:
I'm unable to access the "redis-replica" service as well as the "redis-master" service because Podman Desktop / Podman generates the following service:
When it should be creating this (example from a kompose conversion which works):
TLDR: When working with multiple containers with compose, it does not work well at all when converting to Kubernetes. 1 container is okay though.
Originally posted by @cdrage in https://github.com/containers/podman-desktop/issues/3345#issuecomment-1803022622
Describe the solution you'd like
Improvements is:
redis-replica
notredis-replica-pod-35967
Take inspiration from kompose with regards to conversion practices for services.
Describe alternatives you've considered
No response
Additional context
No response