ansible-libvirt-microos VS hetzner-k3s

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.

This is with the new version not yet released of my tool https://github.com/vitobotta/hetzner-k3s.

It uses k3s as Kubernetes flavor and Hetzner Cloud as provider. For this test I used extremely high concurrency so the tool hung twice of the process because I was hitting the Hetzner API too hard, so I had to interrupt it again and continue.

Excluding the time it paused/hubg due to the API, I calculated around 11 minutes total for the cluster creation. This includes:

- creating all the resources (cloud instances, firewall, load balancer for the Kubernetes API)

Try my project Hetzner-K3s, it’s by far the easiest and quickest way to create and manage clusters in Hetzner cloud. https://github.com/vitobotta/hetzner-k3s

Hi all, if you already use Kubernetes in any capacity or are you interested in it, would you mind spending a few minutes voting in a quick poll and hopefully answering a few questions? I would appreciate your help a ton because it would help me make the right decision and hopefully avoid a costly waste of time.

Everything is in a Github discussion at https://github.com/vitobotta/hetzner-k3s/discussions/296. A huge thank you in advance if you can help with this!

The new release introduces more customisation options for cluster/service CIDRs, cluster DNS, updated manifests for CSI/CCM/autoscaler, and a couple of improvement for creating large clusters. Check it out at https://github.com/vitobotta/hetzner-k3s

If you are already familiar with this tool, I'd love to know how it's worked for you so far. :)

https://github.com/vitobotta/hetzner-k3s

Kubernetes on Hetzner Cloud the easiest way

There’s this cool GitHub project that helps automate a lot of the process for K3s on Hetzner: https://github.com/vitobotta/hetzner-k3s

If you are willing to leave AWS in order to save a lot of money, you have an option in https://github.com/vitobotta/hetzner-k3s