Katenary/katenary
2
0
Fork 3
Code Issues 13 Pull Requests 2 Actions Packages Projects 4 Releases 18 Wiki Activity

Comparison / contrast with Kompose #48

New Issue
Open
opened 2023-01-14 20:05:34 +00:00 by bcdady · 6 comments
bcdady commented 2023-01-14 20:05:34 +00:00 (Migrated from github.com)
Copy Link
Copy Source

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.

I've just now learned of both this tool, and also learned of [Kompose](https://github.com/kubernetes/kompose.git) (from [this kubernetes.io page](https://kubernetes.io/docs/tasks/configure-pod-container/translate-compose-kubernetes/)). 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 commented 2023-01-15 07:40:21 +00:00
Copy Link
Copy Source

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)

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 commented 2023-01-16 04:07:24 +00:00 (Migrated from github.com)
Copy Link
Copy Source

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?

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?
❤️ 1
cdrage commented 2023-11-22 15:16:55 +00:00 (Migrated from github.com)
Copy Link
Copy Source

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 https://github.com/kubernetes/kompose/issues/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.

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 https://github.com/kubernetes/kompose/issues/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.
👍 1
metal3d commented 2023-11-29 22:09:39 +00:00
Copy Link
Copy Source

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
https://github.com/kubernetes/kompose/issues/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
https://github.com/metal3d/katenary/issues/48#issuecomment-1822967623,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAYN4CFY7YWWIJU4SUR6H3YFYJPDAVCNFSM6AAAAAAT3OELUWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRSHE3DONRSGM
.
You are receiving this because you were mentioned.Message ID:
@.***>

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 > <https://github.com/kubernetes/kompose/issues/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 > <https://github.com/metal3d/katenary/issues/48#issuecomment-1822967623>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AAAYN4CFY7YWWIJU4SUR6H3YFYJPDAVCNFSM6AAAAAAT3OELUWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRSHE3DONRSGM> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> >
❤️ 1
metal3d commented 2024-04-04 08:01:54 +00:00
Copy Link
Copy Source

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).

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 commented 2024-10-29 17:11:28 +00:00
Copy Link
Copy Source

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

You can, if possible, now, try the master branch
metal3d pinned this 2025-08-20 06:44:18 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Something isn't working
 dependencies
Pull requests that update a dependency file
 documentation
Improvements or additions to documentation
 duplicate
This issue or pull request already exists
 enhancement
New feature or request
 go
Pull requests that update go code
 good first issue
Good for newcomers
 help wanted
Extra attention is needed
 invalid
This doesn't seem right
 partially fixed
Some fixes are already made in current release / developpement
 question
Further information is requested
 wontfix
This will not be worked on
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
metal3d (Patrice Ferlet)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Katenary/katenary#48