k3s-ansible VS kubernetes

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.

In the field of software development, efficiency and agility are always sought after. In the era of cloud-native apps, traditional deployment techniques—which are frequently laborious and prone to errors—are starting to become obstacles. This is when Kubernetes and GitOps come in handy.

Are you looking for a hassle-free way to deploy Moodle™ Learning Management Systems (LMS) on Kubernetes? Look no further! Krestomatio presents the LMS Moodle Operator, an open-source Kubernetes Operator designed to simplify the deployment and management of Moodle instances on Kubernetes clusters. Let's dive into what makes this tool a great choice for Moodle administrators and developers alike.

Securing access to your Kubernetes clusters is crucial as inadequate security measures can lead to unauthorized access and potential data breaches. However, navigating the complexities of Kubernetes access security, especially when setting up strong authentication, authorization, and network policies, can be challenging.

Deploying AI models into production requires tools that can package applications and manage them at scale. Docker simplifies the deployment of AI applications by containerizing them, ensuring that the application runs smoothly in any environment. Kubernetes, an orchestration system for Docker containers, allows for the automated deployment, scaling, and management of containerized applications, essential for AI applications that need to scale across multiple servers or cloud environments.

To learn more, you can start by exploring the official Kubernetes documentation.

With the containerized Node.js/Express API, I could run multiple containers, scaling to handle more traffic. Using a tool called minikube, we can easily spin up a local Kubernetes cluster to horizontally scale Docker containers. It was possible to keep one shared instance of the database, and many APIs were routed with an internal Kubernetes load balancer.

This package is widely used for powerful CLI builds, it is used for example for Kubernetes CLI and GitHub CLI, in addition to offering some cool features such as automatic completion of shell, automatic recognition of flags (the tags) , and you can use -h or -help for example, among other facilities.

We closely monitor Kubernetes and cloud providers' updates by following official changelogsand using RSS feeds, allowing us to anticipate potential issues and adapt our infrastructure proactively.

"You are holding it wrong", huh?

From the homepage https://kubernetes.io/:

"Kubernetes, also known as K8s, is an open-source system for automating deployment, scaling, and management of containerized applications."

Do you see "not recommended for smaller-scale applications" anywhere? Including on the entire home page? Looking for "small", "big" and "large" also yields nothing.