metal3d
commented
1 year ago 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
cdrage
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.