# k3s Published articles for k3s. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Optimizing OpenFaaS on Kubernetes: Comparative Analysis of Language Runtimes and Cluster Distributions DevFeed: [Optimizing OpenFaaS on Kubernetes: Comparative Analysis of Language Runtimes and Cluster Distributions]() Original publisher: [Read original article]() Author: Ehsan Ataie, Mohammadreza Pooshani, Hossein Aqasizade Published: 2026-10-30T04:00:00Z Content type: comparison Language: en Sources: [arXiv: Distributed Computing](), [arXiv: Software Engineering]() Topics: [OpenFaaS](), [Kubernetes](), [function as a service](), [performance-engineering](), [Go Language](), [Node.js]() Tags: [concurrent](), [cpu](), [cs-dc](), [cs-pf](), [cs-se](), [delay](), [faas](), [go](), [impact](), [infrastructure](), [insights](), [k3s](), [kubernetes](), [latency](), [low-latency](), [metrics](), [node-js](), [performance](), [python](), [runtimes](), [serverless](), [throughput](), [trade]() ### AI overview The study evaluates OpenFaaS on Kubeadm, K3s, MicroK8s, and K0s using CloudLab, comparing Python, Go, and Node.js functions under different levels of concurrent invocation. It measures throughput, CPU usage, and delay. The abstract reports that Go consistently achieves higher throughput and lower CPU usage than Python and Node.js. K3s and Kubeadm perform best among the Kubernetes distributions: K3s shows high throughput, while Kubeadm maintains low latency and efficient CPU usage. The excerpt does not provide detailed measurements or results for MicroK8s and K0s. ### Source excerpt arXiv:2604.05496v2 Announce Type: replace-cross Abstract: Serverless computing, particularly Function-as-a-Service (FaaS), has revolutionized cloud computing by abstracting infrastructure management and enabling dynamic resource allocation. This paper examines the performance and compatibility of OpenFaaS, an open-source serverless platform, when deployed on various Kubernetes distributions, including Kubeadm, K3s, MicroK8s, and K0s. Moreover, leveraging the CloudLab infrastructure, this study examines the impact of Python, Go, and Node$.$js programming languages on the performance of Kubernetes-enabled OpenFaaS, specifically when these languages are used to develop functions deployed on the platform. The performance is evaluated and analyzed under various levels of concurrent invocations using several usage-level metrics, such as throughput and CPU usage, as well as responsiveness metrics, such as delay. According to our findings, Go consistently outperforms Python and Node$.$js in terms of throughput and CPU usage, making it the ideal runtime for serverless applications. Among the Kubernetes distributions, K3s and Kubeadm exhibit superior performance, with Kubeadm maintaining low latency and efficient CPU usage, and K3s demonstrating high throughput. This study provides valuable insights into optimizing the Kubernetes-enabled OpenFaaS platform, highlighting the strengths and trade-offs of different Kubernetes distributions and language runtimes. ## XCP-ng and Xen Orchestra on RISC-V: a progress report from the emulator DevFeed: [XCP-ng and Xen Orchestra on RISC-V: a progress report from the emulator]() Original publisher: [Read original article]() Author: Bruno Verachten Published: 2026-10-23T10:00:06Z Content type: article Language: en Sources: [XCP-ng]() Topics: [RISC-V](), [Xen](), [qemu](), [experience report]() Tags: [ai](), [almalinux](), [ampere](), [arm](), [board](), [boot](), [bug](), [build](), [console](), [containers](), [debian](), [docker](), [emulator](), [k3s](), [progress-report](), [prototype](), [qemu](), [risc-v](), [xen](), [xen-orchestra]() ### AI overview XCP-ng and Xen Orchestra now manage a RISC-V virtualization stack in QEMU on x86: XO can list and operate the host and VMs, and a Debian 13 guest runs Docker and K3s. The setup uses 3 harts and 5 GiB of RAM; it also displays an XFCE desktop in the VM console. It remains an experimental prototype: the full stack has not run on RISC-V hardware, packages are personal and unsupported, and most patches await review. Reported issues include delayed guest IP reporting, a disk-size mismatch in XO, and occasional Docker pull retries. Emulation is slow, with guest disk reads around 800 KB/s and K3s taking about a minute to report Ready. The next goals are booting the full stack on a board, upstreaming patches, and making package builds reproducible. ### Source excerpt XCP-ng on RISC-V now runs in QEMU, managed by Xen Orchestra, with a Debian guest running Docker and K3s. It's a prototype, and here's where it stands. ## Moving from Docker Compose to k3s: Flannel, Traefik and the Gateway API in simple terms DevFeed: [Moving from Docker Compose to k3s: Flannel, Traefik and the Gateway API in simple terms]() Original publisher: [Read original article]() Author: BillaCode Published: 2026-10-13T10:52:20Z Content type: article Language: en Sources: [DevOps.dev]() Topics: [Docker Compose](), [traefik]() Tags: [api](), [backend](), [bootstrap](), [docker-compose](), [flannel](), [gateway-api](), [go](), [helm](), [home-server](), [k3](), [k3s](), [kubernetes](), [microservices](), [open-source](), [production](), [queue](), [scripts](), [traefik](), [transcoder](), [video](), [workers]() ### AI overview The Kithly backend--a Go API, queue workers and a video transcoder--was moved from Docker Compose on a home server to k3s. The article says it will explain why k3s was chosen and clarify the roles of Flannel, Traefik and the Gateway API, then describe the cutover, including an eight-minute production outage. The supplied excerpt ends during a trimmed Compose configuration, so it does not establish the migration steps, how the networking and routing components were configured, or how the outage was resolved. ### Source excerpt Hi Guys, the Kithly backend (a Go API, a few queue workers and a video transcoder) has been running on a home server with Docker Compose... Continue reading on DevOps.dev " ## K3s vs. K8s: When lightweight Kubernetes distros win (and when they don't) DevFeed: [K3s vs. K8s: When lightweight Kubernetes distros win (and when they don't)]() Original publisher: [Read original article]() Author: Peter Smails Published: 2026-10-02T13:00:00Z Content type: comparison Language: en Sources: [Kubernetes Overview, News and Trends | The New Stack](), [The New Stack]() Topics: [k3s](), [Kubernetes](), [CI/CD]() Tags: [architecture](), [attack-surface](), [ci-cd](), [cloud](), [complexity](), [container](), [containers](), [continuous-integration](), [control-plane](), [controller](), [ecosystem](), [edge-computing](), [it](), [k3s](), [k8s](), [kubernetes](), [post-contributed](), [sponsor-suse](), [sponsored-post-contributed](), [suse]() ### AI overview This comparison explains how K3s reduces Kubernetes resource use and operational overhead through a consolidated, lightweight distribution, while standard Kubernetes offers broader flexibility. It outlines use cases including edge deployments, developer environments and CI/CD, and describes situations where standard Kubernetes may be preferable, such as complex or regulated workloads. ### Source excerpt The Kubernetes ecosystem has a complexity problem, and most teams already know it. Standard Kubernetes (K8s) is extraordinarily powerful, but The post K3s vs. K8s: When lightweight Kubernetes distros win (and when they don't) appeared first on The New Stack. ## Docker Swarm Alternatives: Kubernetes, K3s, Nomad, ECS, and OpenShift DevFeed: [Docker Swarm Alternatives: Kubernetes, K3s, Nomad, ECS, and OpenShift]() Original publisher: [Read original article]() Author: Portainer Team Published: 2026-07-29T00:00:00Z Content type: comparison Language: en Sources: [Portainer]() Topics: [Docker](), [Kubernetes](), [Orchestration](), [container](), [migration](), [k3s](), [Network](), [Firewall](), [cloud-infrastructure](), [Portainer]() Tags: [2025](), [compare](), [containers](), [docker](), [firewall](), [k3s](), [kubernetes](), [migrate](), [networking](), [orchestration](), [portainer](), [swarm]() ### AI overview This comparison explains why teams may need alternatives to Docker Swarm, citing breaking changes in Docker Engine v29 and ecosystem shifts. It highlights Kubernetes, K3s, Nomad, Amazon ECS, and Red Hat OpenShift for different container infrastructure needs. ### Source excerpt Looking for Docker Swarm alternatives? Compare Kubernetes, Nomad, Portainer and more to find the best container orchestration platform for your needs. ## Running the Debezium Platform on AWS: PostgreSQL to Amazon Kinesis DevFeed: [Running the Debezium Platform on AWS: PostgreSQL to Amazon Kinesis]() Original publisher: [Read original article]() Author: Philippe Camus Published: 2026-07-24T00:00:00Z Content type: tutorial Language: en Sources: [Debezium]() Topics: [Amazon Web Services](), [Amazon EC2](), [Amazon RDS](), [k3s](), [PostgreSQL](), [RDS for PostgreSQL](), [AWS IAM](), [Deployment](), [identity and access management](), [Kubernetes](), [Replication](), [Monitoring]() Tags: [amazon-rds](), [amazon-web-services](), [aws](), [deployment](), [ec2](), [iam](), [k3s](), [kubernetes](), [monitoring](), [postgresql](), [rds-for-postgresql](), [replication]() ### AI overview A practical guide to running the Debezium Platform on a single-node k3s cluster hosted on Amazon EC2. It configures a change-data-capture pipeline from Amazon RDS for PostgreSQL to Amazon Kinesis, covering AWS IAM, stream naming, logical replication, and deployment automation. ### Source excerpt In his recent mid-year update, Mario highlighted the incredible work he and his team have done to make the Debezium Platform operational on Kubernetes. So let us take it somewhere concrete: Amazon Web Services. This post stands the Platform up on a single-node k3s cluster on an EC2 instance and builds a real change-data-capture pipeline from Amazon RDS for PostgreSQL to Amazon Kinesis. The deployment itself is done through a couple of simple commands via a companion project that does the heavy lifting, so the focus is the AWS-specific friction that documentation is thin on: IAM for the Kinesis sink, Kinesis stream naming, RDS logical replication, and reading a change event back out of the stream to prove it all works. Read more... ## Single-Node Kubernetes GitOps on a Budget DevFeed: [Single-Node Kubernetes GitOps on a Budget]() Original publisher: [Read original article]() Published: 2026-03-04T00:00:00Z Content type: tutorial Language: en Sources: [Gaurav Sarma's]() Topics: [GitOps](), [k3s](), [Argo CD](), [Kubernetes](), [Deployment](), [Self-hosted](), [Firewall](), [TLS (Transport Layer Security)](), [traefik](), [Ubuntu](), [GitHub](), [Digital Ocean]() Tags: [argocd](), [deployment](), [digitalocean](), [firewall](), [github](), [gitops](), [k3s](), [kubernetes](), [lets](), [linux](), [macos](), [self-hosted]() ### AI overview This tutorial describes a budget-conscious, single-node Kubernetes platform built with k3s and GitOps. It covers bootstrapping an Ubuntu VM, syncing applications with ArgoCD, and adding TLS and firewall controls. The supplied text is truncated before the full implementation is presented. ### Source excerpt . [Single-Node Kubernetes GitOps on a Budget](single-node-k3s-gitops-on-a-budget-cover... ## 2026 roundup: Ansible roles, blog migration, K3s on Raspberry Pi, and Lookat 2.1.0 DevFeed: [2026 roundup: Ansible roles, blog migration, K3s on Raspberry Pi, and Lookat 2.1.0]() Original publisher: [Read original article]() Author: Staf Wagemakers Published: 2026-01-04T09:26:00Z Content type: article Language: en Sources: [stafwag]() Topics: [Ansible](), [hosting](), [migration](), [k3s](), [Kubernetes](), [Raspberry Pi](), [Debian](), [releases](), [Unix](), [CI/CD](), [Security]() Tags: [2026](), [ansible](), [ci-cd](), [cloud-init](), [coreboot](), [debian](), [freebsd](), [github](), [hosting](), [k3s](), [kubernetes](), [linux](), [mastodon](), [migration](), [newyear](), [newyear2026](), [plushtodon](), [raspberrypi](), [releases](), [thinkpad](), [w500](), [w541]() ### AI overview A 2026 roundup covering maintained Ansible roles, the migration of a blog from GitHub to personal hosting, a lightweight K3s cluster on three Raspberry Pi 4 devices, updated Debian compatibility, and the Lookat 2.1.0 release. ### Source excerpt You may also enjoy 1 minute read Made some time to do some work for a few Ansible roles that I maintain. You'll find the new releases below. Read more... 2 minute read If you follow my blog posts with an RSS reader, update the rss feed to: ...If you want to continue to follow me off-course ;-) I moved my blog from GitHub to my own hosting ( powered by Procolix ). Procolix sponsored my hosting for 20 years, till I decided to start my company Mask27.dev. ## ansible-k3s-on-vms updated to Debian 13 (Trixie) DevFeed: [ansible-k3s-on-vms updated to Debian 13 (Trixie)]() Original publisher: [Read original article]() Author: Staf Wagemakers Published: 2025-11-13T04:30:00Z Content type: release Language: en Sources: [stafwag]() Topics: [Ansible](), [k3s](), [Debian](), [Raspberry Pi](), [virtual machines](), [Cloud]() Tags: [ansible](), [changelog](), [cloud](), [cloudinit](), [cluster](), [debian](), [debugging](), [k3s](), [kubernetes](), [linux](), [pi](), [pi-4](), [release](), [virtual-machines]() ### AI overview The article announces updated Ansible roles for provisioning virtual machines and deploying k3s on a Raspberry Pi 4 cluster. The roles were updated for Debian 13 Trixie and include new templates, examples, and fixes across several roles. ### Source excerpt I use the lightweight Kubernetes K3s on a 3-node Raspberry Pi 4 cluster. And created a few ansible roles to provision the virtual machines with cloud image with cloud-init and deploy k3s on it. I updated the roles below to be compatible with the latest Debian release: Debian 13 Trixie. With this release comes a new movie ;-) ## Preview: Slice Up Bare-Metal with Slicer DevFeed: [Preview: Slice Up Bare-Metal with Slicer]() Original publisher: [Read original article]() Author: Alex Ellis Published: 2025-08-30T08:09:48Z Content type: release Language: en Sources: [Alex Ellis' Blog]() Topics: [Firecracker](), [Kubernetes](), [OpenFaaS](), [systemd](), [Arch Linux](), [Arm](), [migration](), [Ollama]() Tags: [arm](), [bare-metal](), [boot](), [deploy](), [firecracker](), [k3s](), [kubernetes](), [linux](), [network](), [preview](), [self-hosting](), [slicer](), [storage](), [systemd](), [testing](), [work](), [x86-64]() ### AI overview OpenFaaS Ltd is previewing Slicer, an internal tool that partitions bare-metal hosts into Firecracker microVMs. The article describes use cases including Kubernetes cluster scaling, customer simulations, chaos testing, production troubleshooting, Arm and x86_64 testing, persistent workloads, multi-host deployments, and GPU access for Ollama. ### Source excerpt The easiest and best supported way to learn and deploy Firecracker and microVMs. ## Intel N100 Mini PC for R&D and Self-Hosting Compared with Raspberry Pi 5 DevFeed: [Intel N100 Mini PC for R&D and Self-Hosting Compared with Raspberry Pi 5]() Original publisher: [Read original article]() Author: Alex Ellis Published: 2025-08-18T08:09:48Z Content type: opinion Language: en Sources: [Alex Ellis' Blog]() Topics: [pc](), [intel](), [cpu](), [Self-hosted](), [Raspberry Pi](), [NVMe](), [Firecracker](), [Kubernetes](), [Linux](), [k3s](), [OpenFaaS](), [ddr5]() Tags: [ddr5](), [firecracker](), [github-actions](), [intel](), [k3s](), [kubernetes](), [linux](), [m-2-nvme](), [mini-pc](), [pc](), [processor](), [self-hosting](), [storage](), [threads](), [work]() ### AI overview The article evaluates the low-power Intel N100 Mini PC for R&D and self-hosting, comparing it with the Raspberry Pi 5. It discusses CPU, RAM, NVMe storage, Ethernet, virtualization, Kubernetes, Firecracker, and cost considerations. ### Source excerpt Exploring the capabilities of the Intel N100 Mini PC for work and self-hosting as an alternative to public cloud. ## Kubernetes Networking with Multus DevFeed: [Kubernetes Networking with Multus]() Original publisher: [Read original article]() Author: Techno Tim Published: 2024-04-14T13:00:00Z Content type: tutorial Language: en Sources: [Techno Tim]() Topics: [Kubernetes](), [Network](), [Cilium](), [k3s]() Tags: [cilium](), [homelab](), [k3s](), [kubernetes](), [kubernetes-networking](), [networking](), [video]() ### AI overview A video tutorial covering Kubernetes networking, from CNIs to configuring Multus for traditional networking needs. It includes installation guidance and connectivity and DNS testing steps, with notes for RKE2 and Cilium users. ### Source excerpt I just discovered Multus and it fixed Kubernetes networking! In this video we cover a lot of Kubernetes networking topics from beginner topics like CNIs, to advanced topics like adding Multus for more traditional networking within Kubernetes - which fixes a lot of problems you see with Kubernetes networking. Also, I had to turn the nerd up to 11 on this one. 📺 Watch Video Be sure to ch... ## Fly Kubernetes does more now DevFeed: [Fly Kubernetes does more now]() Original publisher: [Read original article]() Published: 2024-03-07T00:00:00Z Content type: article Language: en Sources: [Fly]() Topics: [Kubernetes](), [fly.io](), [Firecracker](), [k3s](), [container](), [Network](), [API](), [Prometheus]() Tags: [2](), [api](), [cdn](), [close-to-users](), [complexity](), [containers](), [deploy-app-servers](), [docker](), [elixir](), [firecracker](), [fly](), [fly-io](), [heroku-alternative](), [heroku-competitor](), [hosting](), [i](), [k3s](), [kubernetes](), [networking](), [postgresql-clusters](), [prometheus](), [servers]() ### AI overview Fly Kubernetes has moved from early access toward a closed beta as a managed Kubernetes service backed by Fly.io infrastructure. It handles Kubernetes control-plane operations while users deploy workloads. The article explains that Fly's design uses K3s and Virtual Kubelet, transforms containers into Firecracker microVMs, and connects pods through an internal WireGuard mesh. ### Source excerpt Eons ago, we announced we were working on Fly Kubernetes. It drummed up enough excitement to prove we were heading in the right direction. So, we got hard to work to get from barebones "early access" to a beta release. We'll be onboarding customers to the closed beta over the next few weeks. Email us at sales@fly.io and we'll hook you up. Fly Kubernetes is the "blessed path"™ to using Kubernetes backed by Fly.io infrastructure. Or, in simpler terms, it is our managed Kubernetes service. We take care of the complexity of operating the Kubernetes control plane, leaving you with the unfettered joy of deploying your Kubernetes workloads. If you love Fly.io and K8s, this product is for you. What even is a Kubernete? So how did this all come to be--and what even is a Kubernete? You can see more fun details in Introducing Fly Kubernetes. If you wade through all the YAML and CNCF projects, what's left is an API for declaring workloads and how it should be accessed. But that's not what people usually talk / groan about. It's everything else that comes along with adopting Kubernetes: a container runtime (CRI), networking between workloads (CNI) which leads to DNS (CoreDNS). Then you layer on Prometheus for metrics and whatever the logging daemon du jour is at the time. Now you get to debate which Ingress--strike that--Gateway API to deploy and if the next thing is anything to do with a Service Mess, then as they like to say where I live, "bless your heart". Finally, there's capacity planning. You've got to pick and choose where, how and what the Nodes will look like in order to configure and run the workloads. When we began thinking about what a Fly Kubernetes Service could look like, we started from first principles, as we do with most everything here. The best way we can describe it is the scene from Iron Man 2 when Tony Stark discovers a new element. As he's looking at the knowledge left behind by those that came before, he starts to imagine something entirely different and ## First Impressions with the Raspberry Pi 5 DevFeed: [First Impressions with the Raspberry Pi 5]() Original publisher: [Read original article]() Author: Alex Ellis Published: 2023-09-28T10:55:07Z Content type: article Language: en Sources: [Alex Ellis' Blog]() Topics: [Raspberry Pi](), [OpenFaaS](), [CI/CD](), [Open Source]() Tags: [actions](), [arm](), [bare-metal](), [benchmarking](), [ci](), [cloud](), [cluster](), [docker](), [emulation](), [firecracker](), [github](), [github-actions](), [headless](), [homelab](), [installer](), [k3s](), [kubernetes](), [pi-5](), [raspberry-pi](), [raspberry-pi-5](), [raspberrypi](), [server](), [servers](), [upgrade]() ### AI overview The author uses Raspberry Pis mainly as headless, low-power servers and build machines: for OpenFaaS functions, isolated CI runners, K3s clusters installed with k3sup, and native Arm builds through GitHub Actions runners wrapped by actuated in Firecracker VMs. The Raspberry Pi 5 adds a PCIe port and power button, and moves some board components; the author highlights deeper silicon changes but the excerpt does not specify them. The author says the Pi 4 already outperforms QEMU emulation on fast servers for Arm builds. This excerpt provides no Pi 5 performance measurements or upgrade recommendation, so it cannot establish whether upgrading is worthwhile. ### Source excerpt For someone who runs the Raspberry Pi as a server, build agent and for Kubernetes, how does the new version stack up? And should you upgrade? ## Fully Automated K3S etcd High Availability Install DevFeed: [Fully Automated K3S etcd High Availability Install]() Original publisher: [Read original article]() Author: Techno Tim Published: 2022-03-26T15:00:00Z Content type: tutorial Language: en Sources: [Techno Tim]() Topics: [k3s](), [Ansible](), [Kubernetes](), [Availability](), [Deployment]() Tags: [ansible](), [deployment](), [high-availability](), [k3s](), [kubernetes](), [provisioning]() ### AI overview A tutorial for automating the setup of a highly available k3s cluster using etcd, MetalLB, kube-vip, and Ansible. It covers prerequisites, VM provisioning, repository configuration, and cluster deployment. ### Source excerpt Setting up k3s is hard.That's why we made it easy.Today we'll set up a High Availability K3s cluster using etcd, MetalLB, kube-vip, and Ansible.We'll automate the entire process giving you an easy, repeatable way to create a k3s cluster that you can run in a few minutes. A HUGE THANKS to our sponsor, Micro Center! New Customers Exclusive - Get a Free 240gb SSD at Micro Center: https://micro.c... ## A Hypervisor Built on Kubernetes - Cloud Native HCI with Harvester DevFeed: [A Hypervisor Built on Kubernetes - Cloud Native HCI with Harvester]() Original publisher: [Read original article]() Author: Techno Tim Published: 2022-03-12T13:00:00Z Content type: article Language: en Sources: [Techno Tim]() Topics: [Kubernetes](), [rancher](), [virtual machines](), [Open Source](), [k3s](), [Linux](), [Windows]() Tags: [high-availability](), [k3s](), [kubernetes](), [linux](), [open-source](), [rancher](), [virtual-machines](), [windows]() ### AI overview The article introduces Harvester, an open-source hypervisor from Rancher built on Kubernetes. It describes running and scaling Linux and Windows virtual machines, providing high availability, and creating RKE1, RKE2, and K3S Kubernetes clusters alongside those virtual machines. ### Source excerpt Rancher released a next generation open source HCI software hypervisor built on Kubernetes that helps you run virtual machines.With Harvester you can create Linux, Windows, or any virtual machine that can be easily scaled and cluster giving your high availability virtual machines with a few clicks.It also gives you a platform to automatically create HA RKE1, RKE2, and K3S Kubernetes clusters wi... ## TrueNAS Scale Apps - Official, Unofficial, Docker, and Kubernetes DevFeed: [TrueNAS Scale Apps - Official, Unofficial, Docker, and Kubernetes]() Original publisher: [Read original article]() Author: Techno Tim Published: 2022-03-02T13:00:00Z Content type: tutorial Language: en Sources: [Techno Tim]() Topics: [truenas](), [App](), [Docker](), [Kubernetes](), [Deployment](), [k3s](), [Docker Image]() Tags: [applications](), [apps](), [deployment](), [docker](), [docker-image](), [k3s](), [kubernetes](), [truenas]() ### AI overview A tutorial on installing and managing applications in TrueNAS SCALE, including official, unofficial, and community apps, Docker images, and Kubernetes deployments with Helm. It discusses the app engine's support for Docker, Kubernetes, and K3S. ### Source excerpt TrueNAS SCALE is here and with it comes new way of installing and managing applications.You can install official apps, unofficial and community apps using TrueCharts, and also any Docker image or Kubernetes deployment with helm.Join me as we dive into managing applications and exploring TrueNAS SCALES's new app engine that runs Docker, Kubernetes, and K3S. 📺 Watch Video If you're looking fo... ## Incrementally measuring my internet speed with Prometheus DevFeed: [Incrementally measuring my internet speed with Prometheus]() Original publisher: [Read original article]() Author: Carlos Alexandro Becker Published: 2021-07-29T00:00:00Z Content type: tutorial Language: en Sources: [Carlos Becker]() Topics: [Prometheus](), [Internet](), [Grafana](), [Time Series](), [dashboards](), [k3s](), [Terraform](), [Helm charts]() Tags: [cache](), [dashboard](), [grafana](), [helm-charts](), [internet](), [k3s](), [measuring](), [metrics](), [modem](), [prometheus](), [providers](), [terraform](), [time-series]() ### AI overview A tutorial on measuring home internet speed every 30 minutes with a custom Prometheus exporter, storing the results in a time-series database, and visualizing them in Grafana. ### Source excerpt I live in Brazil, and, if you're not familiar, internet usually sucks here. ## Configuring Traefik 2 Ingress for Kubernetes DevFeed: [Configuring Traefik 2 Ingress for Kubernetes]() Original publisher: [Read original article]() Author: Techno Tim Published: 2021-04-08T14:00:00Z Content type: tutorial Language: en Sources: [Techno Tim]() Topics: [traefik](), [Kubernetes](), [k3s](), [rancher](), [Cloudflare]() Tags: [certificates](), [cloudflare](), [helm](), [high-availability](), [homelab](), [ingress](), [k3s](), [kubernetes](), [rancher](), [self-hosting](), [ssl](), [traefik](), [tutorial]() ### AI overview A tutorial for configuring Traefik 2 as the ingress controller on a highly available k3s Kubernetes cluster, including Rancher compatibility, external load balancing, and wildcard certificates stored on persistent storage. ### Source excerpt This guide is for installing traefik 2 on k3s.If you're not using rancher, that's fine, just skip to Reconfiguring k3s Note: There is an updated tutorial on installing traefik + cert-manager on Kubernetes here. However, if you want to store your certificates on disk, this tutorial here is perfectly fine. It assumes you have followed: Fully Automated K3S etcd High Availability Install ... ## Multi-CPU Architecture Kubernetes Cluster with a Raspberry Pi DevFeed: [Multi-CPU Architecture Kubernetes Cluster with a Raspberry Pi]() Original publisher: [Read original article]() Author: Techno Tim Published: 2021-03-14T14:00:00Z Content type: tutorial Language: en Sources: [Techno Tim]() Topics: [Kubernetes](), [k3s](), [Raspberry Pi](), [Docker](), [Ubuntu](), [cpu](), [x86]() Tags: [arm](), [cpu](), [docker](), [k3s](), [kubernetes](), [raspberry-pi](), [ubuntu](), [x86]() ### AI overview A video tutorial shows how to build a multi-architecture Kubernetes cluster by adding an ARM-based Raspberry Pi 4 running Ubuntu and k3s to an existing x86 cluster. It also discusses CPU-specific Docker images and configuration requirements. ### Source excerpt Building a Multi-architecture CPU Kubernetes cluster is easier than you think with k3s.In this video we'll build a Raspberry Pi 4 with an ARM CPU and add it to our existing x86 x64 amd64 CPU Kubernetes cluster.Our foundation will be Ubuntu for ARM, then we'll add k3s, and then join it to our cluster.We'll also discuss how this works with Docker images built for specific CPU types.We'll also tal... ## Tutorial: Installing Rancher on a High-Availability k3s Cluster DevFeed: [Tutorial: Installing Rancher on a High-Availability k3s Cluster]() Original publisher: [Read original article]() Author: Techno Tim Published: 2020-12-19T14:00:00Z Content type: tutorial Language: en Sources: [Techno Tim]() Topics: [k3s](), [Kubernetes](), [rancher](), [Homelab](), [configuration]() Tags: [clusters](), [health](), [helm](), [high-availability](), [homelab](), [install](), [k3s](), [kubernetes](), [load-balancer](), [rancher](), [tutorial]() ### AI overview A step-by-step tutorial for installing Rancher on an existing high-availability k3s cluster. It covers configuring a load balancer, installing Helm and cert-manager, configuring Rancher, using the GUI, scaling the cluster, and setting up health and liveness checks. ### Source excerpt Are you running Kubernetes in your homelab or in the enterprise? Do you want an easy way to manage and create Kubernetes clusters? Do you want high availability Rancher? Join me as we walk through stalling Rancher on an existing high availability k3s cluster in this step-by-step tutorial.We install Rancher, configure a load balancer, install and configure helm, install cert-manager, configure ... ## Portainer 2.0: Installing and Managing Kubernetes with k3s, k3d, and kubectl DevFeed: [Portainer 2.0: Installing and Managing Kubernetes with k3s, k3d, and kubectl]() Original publisher: [Read original article]() Author: Techno Tim Published: 2020-08-29T14:00:00Z Content type: tutorial Language: en Sources: [Techno Tim]() Topics: [Portainer](), [Kubernetes](), [Tutorial](), [k3s](), [kubectl]() Tags: [commands](), [how-to](), [k3s](), [kubectl](), [kubernetes](), [portainer](), [tutorial]() ### AI overview A step-by-step tutorial for installing Portainer 2 with Kubernetes. It sets up k3s using k3d, installs kubectl, launches Portainer, and runs a Minecraft server in Kubernetes as a proof of work. ### Source excerpt What's new in Portainer 2.0? Well, a ton.With the release of Portainer 2 you now have the option to install Kubernetes.This makes installing, managing, and deploying Kubenetes really easy.In this step by step tutorial, we'll start with nothing and end up with a fully working Portainer 2 server running Kubernetes.We'll set up k3s using k3d, install kubectl, and then spin up Portainer.As an adde... ## NVIDIA Jetson Nano - Docker optimized Linux Kernel DevFeed: [NVIDIA Jetson Nano - Docker optimized Linux Kernel]() Original publisher: [Read original article]() Published: 2019-05-04T01:57:21Z Content type: tutorial Language: en Sources: [Hypriot]() Topics: [Jetson](), [Linux Kernel](), [Docker](), [k3s](), [Kubernetes](), [Network](), [Ubuntu]() Tags: [build-system](), [developer](), [docker](), [jetson](), [k3s](), [kubernetes](), [linux-kernel](), [networking](), [robotics](), [ubuntu]() ### AI overview This tutorial explains how to customize and build a Linux kernel directly on the NVIDIA Jetson Nano DevKit. It focuses on adding kernel settings, including IPVLAN, needed for networking with Docker Swarm, Kubernetes, and k3s, and covers preparing the build environment and downloading the kernel sources. ### Source excerpt Despite the fact that the NVIDIA Jetson Nano DevKit comes with Docker Engine preinstalled and you can run containers just out-of-the-box on this great AI and Robotics enabled board, there are still some important kernel settings missing to run Docker Swarm mode, Kubernetes or k3s correctly. So, let's try to fix this... Analyzing the Linux Kernel In my last blogpost Verify your Linux Kernel for Container Compatibility, I already shared all the details how you can easily verify the Linux kernel for all Container related kernel settings. So, this first part of analyzing the capabilities of the stock Linux kernel 4.9.x provided by NVIDIA is already done and documented. And this was an easy task as well, so everyone who's interested in these details can repeat the task at his/her own device. Let's recap what we did found. Especially there is one important setting which will be used for networking. This feature called "IPVLAN", is required for Docker Swarm mode and it's also used for networking in Kubernetes and k3s. Building your own Linux Kernel Anyway, even when we'd like to include or change only a single kernel setting, we have to customize the kernel configuration and have to compile and build our own Linux kernel. This is typically a common task for a desktop Linux system, but can be pretty ugly and cumbersome if you have to build the kernel for an Embedded Device. When we look back to all the other NVIDIA Jetson boards, like the TK1, TX1 and TX2, this requires a second Linux machine, running Ubuntu 14.04 or 16.04 on an Intel CPU. Then setting up a complete build system for cross-compiling and all these stuff. Honestly, this is a well-known approach for an Embedded Developer, but the good thing now for the Jetson Nano DevKit this is not required any more. Here the good news: you can customize and build your own Linux kernel directly on the Jetson Nano DevKit! You only need an internet connection and some time to perform all steps on your own. BTW, and this is another