ansible-libvirt-microos VS deckhouse

I've been using a 3 nuc (actually Ryzen devices) k3s on SuSE MicroOS https://microos.opensuse.org/ for my homelab for a while, and I really like it. They made some really nice decisions on which parts of k8s to trim down and which Networking / LB / Ingress to use.

The option to use sqlite in place of etcd on an even lighter single node setup makes it super interesting for even lighter weight homelab container environment setups.

I even use it with Longhorn https://longhorn.io/ for shared block storage on the mini cluster.

If anyone uses it with MicroOS, just make sure you switch to kured https://kured.dev/ for the transactional-updates reboot method.

I'd love to compare it against Talos https://www.talos.dev/ but their lack of support for a persistent storage partition (only separate storage device) really hurts most small home / office usage I'd want to try.

What are the advantages of your project over conceptually similar projects that already exist, like MicroOS (https://microos.opensuse.org/) ?

I would suggest you to check either Leap Micro or MicroOS out.

I use MicroOS (https://microos.opensuse.org/), to keep the base operating system clean you'd install helper tools for constructing containers in a container... so two levels of containers would be very helpful

Where OpenSuse is interesting, definitely, it's with the MicroOS concept of Immutable Installs + their strategy of btrfs snapshots - this looks absolutely great from a stability standpoint ; there are other possible strategies out there, but these people are building a truly unbreakable distro and that's fantastic.

I'm currently running/testing openSUSE's new MicroOS which is really nice but still needs some work

Hi! I just wanted to drop by ansible-libvirt-microos ; since I'm using MicroOS already on a personal server, I decided to make better usage of it, by converting it into a VM host, and setting up another VM inside so that I can deploy more vms with extra steps containers via k3s.

And while k3s sounds easy, it's not after even a slightly larger scale.

If one willing to have in-house k8s today I would recommend https://deckhouse.io/ (I'm not affiliated with them)

Deckhouse

Check Deckhouse as well (https://github.com/deckhouse/deckhouse). Cilium integration was added there recently.

Release Deckhouse v1.26.0 · deckhouse/deckhouse (github.com)

Consider Deckhouse as another option that can be installed everywhere: bare metal, private and public clouds. It has an Open Source core offered in Community Edition, but the pricing for Enterprise Edition is also a fit for small companies. All configuration is made via Custom Resources, all routines (like updating Kubernetes versions and related system components) are automated.

We use cert-manager in our K8s platform for years and it works perfectly. I don't think there is any chance today to compete with it in terms of community adoption. I also can't find any GitHub links for your project which is the most widely accepted way to become trusted by the community — simply because it covers all the basic needs everyone got used to (in the Open Source world): we can see how the code is developed, we can contribute to it, discuss the issues and concerns we have, etc.

We use Vector to ship logs to different storages (including Loki). You can even find the implementation here, however, I am not sure how useful it might be since it's quite specific (Golang hooks for addon-operator). Our manifests are available there as well.