Comparison / contrast with Kompose

[bcdady]

I've just now learned of both this tool, and also learned of Kompose (from this kubernetes.io page).

Could the contributors/maintainers help clarify benefits or difference that might help me appreciate if Katenary might be a better tool for my use case, when compared to Kompose?

At first glance, there appear to be many similarities. The fact that Kompose is part of the 'Kubernetes' organization (in GitHub as well as being referenced from the aforementioned Kubernetes.io docs) seems to suggest it may be a more active/useful tool to consider.

Perhaps an acknowledgement of the Kompose tool and a brief explanation of when/why/how Katenary might be a beneficial choice would help the larger container user community understand the value proposition.

[metal3d]

Hi,
First, I have some enhancement to apply to Katernary. I am very busy between my work and my child born this year, and I admit that I have difficulty managing everything. :)

The benefits is that:

• Kompose actually creates an export “transposed” into raw objects, even if the target is "helm"
• With Katernary there is a "values.yaml" file where created to make installation very easy to tweak
• there are many ways to create volumes like reading files to mount as ConfigMap for example
• I'm currently appending labels to manage helm dependencies
• Katenary proposes some configuration to adapt environment mapping (for example, when the value is linked to the release name)
• Katenary manages the "depends_on" when a service needs to wait another

Of course, Katenary is not perfect. Kompose has got many benefits (for example, it let you choose the target type, while Katenary exclusively uses helm)

[bcdady]

Wow, congratulations @metal3d on the new baby!

This is really great context; thank you!
I tried out Kompose a bit, and provided some feedback on that project.

I'll give Katenary a try now too. I think the values file and depend_on features might be really useful in this project.

Would you consider if helpful if I werw to summarize your list above into a new 'Why Katenary' section in the README?

[cdrage]

Just saw this now, I wanted to let you know @bcdady a big thanks for this tool. Kompose hasn't been able to maintain the Helm support for the last couple of years as Helm continued to move very fast.

With your consent, could we add a link to your tool when we eventually close kubernetes/kompose#1716 ? We'll add it to the README / direct users to your tool as the support for compose to helm is a lot more superior than what we have in Kompose at the moment.

[metal3d]

Hi. Of course you can 🙂 I'm currently fixing last issues I've got for the next release that will provide a lot more features. It's a bit complicated as I just start a new job in a new company. Le mer. 22 nov. 2023, 16:17, Charlie Drage ***@***.***> a écrit :

…

Just saw this now, I wanted to let you know @bcdady <https://github.com/bcdady> a big thanks for this tool. Kompose hasn't been able to maintain the Helm support for the last couple of years as Helm continued to move very fast. With your consent, could we add a link to your tool when we eventually close kubernetes/kompose#1716 <kubernetes/kompose#1716> ? We'll add it to the README / direct users to your tool as the support for compose to helm is a lot more superior than what we have in Kompose at the moment. — Reply to this email directly, view it on GitHub <#48 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAYN4CFY7YWWIJU4SUR6H3YFYJPDAVCNFSM6AAAAAAT3OELUWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRSHE3DONRSGM> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[metal3d]

The develop branch is, ASAIK, working with my local examples. I need a proper testing mecanism and I will release a V3-alpha as soon as possible.

Sorry for the delay. My life has been a little too busy lately, but I swear I'm doing my utmost to get this version out as soon as possible.

Hopefully, before the end of April 2024 (certainly sooner).

[metal3d]

You can, if possible, now, try the master branch