ezdc VS kompose

Oh for fucks sake…

Let’s reengineer the entire system… AGAIN…

Instead of blessing an existing tool that would have instantly solved the problem their customers had, without requiring internal development… https://kompose.io … tada… it’s a tool the kubernetes community maintains to convert from docker compose files to kubernetes yaml

The team behind TrueNAS (iX Systems) has been steadily eroding the respect I have for them on a year on year basis for half a decade… which is really annoying because they make and maintain the easiest to use ZFS based NAS platforms.

It’s genuinely frustrating that like “how long before they kill it” being my reaction to anything new from Google, my reaction to iX Systems announcing something like this has become an automatic “yeah and what are you changing next?”

Also… what the fuck is anyone doing using Docker Compose in this day and age… I see two scenarios “enterprise retraining costs” and “home users who think kubernetes is just so much more complicated than compose files and they don’t want to learn a new tool when they’re just slapping a database container next to their docker container for this years automated piracy or media management tool of choice”… and in both scenarios management should have asked the crucial question “do we actually need to do anything to support them?” You ask this so you can decide if changes are justified, and by asking this… this is the question that lets you discover ways to leverage third parties to support use cases and save yourself a lot of stupid effort.

My day was off to such a good start… damn it… now I know this fucking update is in my future… maybe this will be the final push and I just fucking buy a Qnap because I’m sick of what feels like every second major release of TrueNAS significantly overhauling things in a way that seamlessly works with my data on disk, sometimes wont break 80% of the software running on the box to interact with that data, and just about always breaks 20% of that software… and having that 20% of software that breaks every time, be the most fucking annoying stuff to fix.

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/)!