k3s-ansible VS k3sup

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.

# Maintainer: Talha Altinel pkgname=k3sup pkgver=0.13.0 pkgrel=1 pkgdesc='A tool to bootstrap K3s over SSH in < 60s' arch=('x86_64') url='https://github.com/alexellis/k3sup' license=('MIT') depends=('glibc' 'openssh') makedepends=('git' 'go>=1.20') source=("${pkgname}-${pkgver}.tar.gz::https://github.com/alexellis/k3sup/archive/${pkgver}.tar.gz") sha256sums=('24939844ac6de581eb05ef6425c89c32b2d0e22800f1344c19b2164eec846c92') _commit=('1d2e443ea56a355cc6bd0a14a8f8a2661a72f2e8') build() { cd "$pkgname-$pkgver" export CGO_CPPFLAGS="${CPPFLAGS}" export CGO_CFLAGS="${CFLAGS}" export CGO_CXXFLAGS="${CXXFLAGS}" export CGO_LDFLAGS="${LDFLAGS}" export GOFLAGS="-buildmode=pie -trimpath -mod=readonly -modcacherw" go build \ -ldflags "-s -w -X github.com/alexellis/k3sup/cmd.Version=$pkgver -X github.com/alexellis/k3sup/cmd.GitCommit=$_commit" \ -o k3sup \ . for shell in bash fish zsh; do ./k3sup completion "$shell" > "$shell-completion" done } package() { cd "$pkgname-$pkgver" install -Dm755 -t "$pkgdir/usr/bin" k3sup mkdir -p "${pkgdir}/usr/share/bash-completion/completions/" mkdir -p "${pkgdir}/usr/share/zsh/site-functions/" mkdir -p "${pkgdir}/usr/share/fish/vendor_completions.d/" install -Dm644 bash-completion "$pkgdir/usr/share/bash-completion/completions/k3sup" install -Dm644 fish-completion "$pkgdir/usr/share/fish/vendor_completions.d/k3sup.fish" install -Dm644 zsh-completion "$pkgdir/usr/share/zsh/site-functions/_k3sup" install -Dm644 -t "$pkgdir/usr/share/licenses/$pkgname" LICENSE }

I recommend learning docker first, then pick a vps host from vpsbenchmarks, then use k3sup to deploy a kubernetes cluster on that, then follow a getting-started kubernetes tutorial from there. You'll also want to buy a domain name with tld-list and then provision a TLS certificate with cert-manager and letsencrypt (skip steps 1-4 because Google Cloud is overpriced).

I just installed k3s yesterday using k3sup on 6 VMs (3 masters, 3 workers) each with 2GB RAM ( limited by the actual RAM on hardware, for now ) with Ubuntu 22.04 as the base OS.

k3s installed with k3sup, longhorn for storage, kube-vip for API VIP, and MetalLB for service load balancer using local subnet, and of course Rancher.

My applause to Alex Ellis for writing a clear, direct call to arms!

Their work is super useful and interesting. I've added them to my list of sponsorships: https://github.com/sponsors/alexellis

Yeah, this is the answer, but I would use this with K3S: https://github.com/alexellis/k3sup

$ curl -sLS https://get.k3sup.dev | sh x86_64 Downloading package https://github.com/alexellis/k3sup/releases/download/0.12.12/k3sup as /home/ec2-user/k3sup Download complete. ============================================================ The script was run as a user who is unable to write to /usr/local/bin. To complete the installation the following commands may need to be run manually. ============================================================ sudo cp k3sup /usr/local/bin/k3sup ================================================================ alexellis's work on k3sup needs your support https://github.com/sponsors/alexellis ================================================================ No nos devolverá nada, pero podremos correr lo siguiente para saber si k3sup efectivamente se instalo: