k3s-ansible VS k3os

I deployed k3s to a test node using Techno Tim's k3s-ansible playbook.

Remind myself about how Ansible works (I've forked this: https://github.com/techno-tim/k3s-ansible/tree/master and added a role to automatically set up my Hetzner server and install Core OS, as well as staring the cluster with Flannel Wireguard Native, and a few other minor changes).

I think this one is updated https://docs.technotim.live/posts/k3s-etcd-ansible/

I recently broke my cluster somehow (see this thread) so I decided to start fresh because I can't get K3s up and running again. I now have 5 nodes (3 master, 2 worker) with etcd configured using the K3s-ansible guide found here. Is it possible to recover the PVs from my failed cluster? I still have SSH access to each of the machines that participated in the cluster. It would save me a lot of rebuilding time if I could extract them (even from an older backup, if Longhorn stores them in an accessible format) and apply to the new cluster.

Like u/darkstar_01 mentioned, I'd start with k3s since it has a lot of these things built in and is really lightweight. To further that suggestion I'd recommend using u/Techno-Tim k3s-ansible playbook, it's dark magic. https://github.com/techno-tim/k3s-ansible

To be honest, I'd just switch to Kubernetes for something like this. Technotim has some pretty easy to digest guides on how to get a basic cluster set up

take a look at this https://github.com/techno-tim/k3s-ansible https://www.youtube.com/watch?v=CbkEWcUZ7zM&ab\_channel=TechnoTim

I'm having a hard time understanding how to setup the network/cluster for HA. I've basically been following along with this guide: https://docs.technotim.live/posts/k3s-etcd-ansible/ which uses MetalLB + kube-vip. I have the cluster running and have the MetalLB IP range set for a block of internal LAN IPs / Layer 2 (unsure if this is correct for what I'm looking to do). All of this seems to be working internally. My confusion is how to get WAN traffic in.

I’m Nomsplease on GitHub, and I’m currently running the latest Proxmox 7.x with the opt-in kernel 6.X. https://github.com/techno-tim/k3s-ansible

Proxmox is host to a bunch of VMs, including a K3S cluster that is setup though an Ansible playbook. There are 3 Masters and 4 workers. I followed TechnoTim’s guide here to get this cracking and honestly, I’ve only scratched the surface on Kubernetes. I setup a bash alias on the first IP in the K3S stack to run the Ansible playbook with one simple command, so its simple to spin up again, should I shutoff this server. I then setup Rancher to maintain and utilize the Kubernetes Cluster, with a Traefik2 ingress, MetalLB, Helm, and Longhorn for distributed storage. Links here for tutorials by TechnoTim – Longhorn, Traefik-K3S-ingress with Cert-manager, and Rancher setup. The Proxmox server is also home to two separate PBX solutions, they’re installed and they have access to my SIP trunk provider (voip.ms, here’s my referral link if anyone’s interested.) I’ve added 15 bucks to the account and have it as a work line should I ever get my Technical Consulting business off the ground. Right now the PBXs can be spun up but the IP phones are sitting in a closet. It’s a cool project to get going though even if I don’t need a landline, let alone a full PBX. From there I have a bunch of small Ubuntu VMs that I have a created though template’s with cloud-init drives to make it a sinch to spin up another VM (Cloud-init tutorial) I just started to get into Terraform (IoC – infrastructure as code) to spin up VMs in much the same way you would with Ansible (project here thru The Digital Life, yt channel). LibreNMS is another thing that I just spun up the other day. No real tutorial to link because SNMP is dead simple. I’m sure I could dockerize some of these projects, rather than spinning up a whole new Ubuntu VM, but sometimes its nice to just have a clean start and then combine Compose files into stacks though I’m sure some of the VMs can be setup to run more than one service per VM.

I still don't forgive SUSE for buying Rancher and then unceremoniously killing k3os. They just left the website up and everything, made no announcement, made no attempt to help the community take over, just left the Github repo to rot: https://k3os.io/

Hard to have confidence in SUSE's commitment to another open source operating system side project after that. SUSE's announcement at the time:

Like SUSE, Rancher is 100% open source and equally as passionate as SUSE about true open source innovation, community empowerment, and customer success. SUSE and Rancher share the same goal – happy and satisfied customers.

https://www.suse.com/c/suse-acquires-rancher/

k3os is no longer supported by Rancher: https://github.com/rancher/k3os/issues/846 I've been keeping mine up to date with https://github.com/BlueKrypto/k3os

[0] https://docs.k3s.io/installation/ha-embedded [1] https://k3os.io/

I (still) run k3os, but it's dead since SUSE bought rancher. (see https://github.com/rancher/k3os/issues/846)

virt-install --install \ --memory 2048 \ --os-type linux \ --os-variant ubuntu20.04 \ --disk size=20 \ --graphics=none \ --name k3os \ kernel=https://github.com/rancher/k3os/releases/download/v0.21.5-k3s2r1/k3os-vmlinuz-amd64,initrd=https://github.com/rancher/k3os/releases/download/v0.21.5-k3s2r1/k3os-initrd-amd64,kernel_args='k3os.fallback_mode=install k3os.install.iso_url=https://github.com/rancher/k3os/releases/download/v0.21.5-k3s2r1/k3os-amd64.iso k3os.install.silent=true k3os.install.tty=ttyS0 console=ttyS0 k3os.install.device=/dev/vda k3os.password=hunter2'

I'm personally fond of https://k3os.io for my small to medium hobby and professional clusters. It comes with a lot the bells and whistles, but is also pretty minimum and just scales easily.

I really liked K3OS, but I feel like Rancher is no longer supporting it. The last commit on the k3os repo is from April, and before those three commits, November of last year. When Rancher decided to move their HCI offering, Harvester, over to RancherOS V2 being based on cOS toolkit/OpenSuse, I don't have high hopes that K3OS will be maintained.

I run k3os on an old laptop with a broken screen.