awesome-operators VS kompose

> Awesome operators

https://github.com/operator-framework/awesome-operators archived since 2021 and now https://operatorhub.io/

I hadn't heard of this, interesting. Layers and layers of abstractions. What an interesting way to solve things. "It's YAML all the way down"?

We have seen in this example how Kubernetes Operators can allow us to automate cloud infrastructure logic. But there are of course a lot more uses to operators, and you can check this list of operators in the wild.

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/