@worldofgeese it's not exactly the same. Katenary creates a helm chart with several values that you can change, it also creates init containers to wait services and I'm currently developing the dependency management.
There a many bugs I fixed.
Next release will be fully documented and production ready. The company where I work is testing it a lot.

@metal3d first time I've heard of it but I think I'll take it for a test drive for an article I wrote (and will re-write) on migrating from Compose to K8s!

@worldofgeese I don't communicate a lot for now because I'm fixing many things following issues reported by my teammates. I think that a new release will be done before the end of the week 😉

@metal3d please let me know! I'll be excited to give it a go.

@metal3d you can see the article I wrote for garden.io on migrating from Compose to K8s at garden.io/blog/migrating-docke. If you see anything that jumps out to you that katenary would have done better than kompose feel free to reach out :-)

@worldofgeese I read when I've got time, but actually yes, there are some points that I don't agree 🙂 E.g. "You'll never scale past one machine because Compose is single node only." => Compose allow the use of Swarm for example

Suivre

@worldofgeese And to answer the question, when you create your helm chart by changing values, variables, and so on... Katenary does it automatically. Actually, what you did in the article takes a few seconds with Katenary.

Inscrivez-vous pour prendre part à la conversation
techlover

Technology lovers, here we are — (development, digital artwork, science…)