ansible-libvirt-microos VS azure-k3s-cluster

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.

If anyone wants a ready-to-go Azure template to play around, here you go:

https://github.com/rcarmo/azure-k3s-cluster

(I tweak this every now and then since I both used it as a training sample for my customers/peers and as a way to run my own batch processes as cheap as possible)

The runtime controller is uwsgi, which acts as supervisor for all processes of an app _or_ embeds the right interpreter-it's pretty much perfect for that, as it also has a cron scheduler and an on-demand, fire-up-an-interpreter-upon-request mode.

As to the k3s stuff, it's all here: https://github.com/rcarmo/azure-k3s-cluster. I update this from time to time as I occasionally nuke the entire cluster and rebuild it (I use AKS for non-hobby workloads, but a single master is just fine for most of my stuff).