timoni VS kompose

Let's see if https://github.com/stefanprodan/timoni will bring some fresh air, knowing Cuelang I think it has the potential for doing so.

There is also https://timoni.sh leveraging CUE to build a better helm.

To be less flippant, there’s cue, jsonnet, and more esoteric things like https://github.com/stefanprodan/timoni coming up

We use CUE directly to generate yaml resources

Have our eyes on Timoni https://github.com/stefanprodan/timoni

https://timoni.sh is the latest kid in town

Install Kompose - a conversion tool that allows you to convert your Docker Compose code to Kubernetes configuration files Run kompose convert in the same directory as your docker-compose.yml to generate the config files for your Kubernetes cluster

Kubernetes (via kompose)

As stated on their homepage, with Kompose, you can now push the same file to a production container orchestrator!. The tool definitely covers a wide range of Kubernetes features, among which these are meaningless locally but crucial for kubernetes :

K3s is a small, open source, no nonsense, distribution of Kubernetes. I think you'll find it just as easy to setup as Swarm. The challenge will be that Kubernetes has an entirely different API compared to Docker/Docker Compose. This can be mitigated by a tool called kompose, but using this will limit what you can do on Kubernetes.

Although I recently moved my own services from docker compose to kubernetes using https://kompose.io/ and now the only thing I run with docker compose, currently, is my private docker registry but everything including in kube, are always in their own folders.

I haven't run into the need to do that, but there is the Kompose project that exists to help with the conversion (https://kompose.io/)!

Compose claims to do that. https://kompose.io and https://kubernetes.io/docs/tasks/configure-pod-container/translate-compose-kubernetes/