Articles tagged with "edge-computing"
Running Prometheus Agent mode on K3s edge clusters can leave stale values in your central dashboard when a target disappears, depending on how stale markers are handled. Here's how to design K3s edge monitoring correctly.
We set up automated upgrades with K3s's system-upgrade-controller, and the Plan stopped progressing on a single node. The culprits were PodDisruptionBudgets and taints. Here's how the mechanism works, how to recover, and how Kubo helps.
K3s's embedded registry mirror (Spegel) is supposed to work cluster-wide, but a newly added edge node alone failed to pull images. The cause: an undistributed registries.yaml, credential drift, and a known containerd 2.0 bug. Here's the correct distribution workflow for air-gapped operations.
K3s and MicroShift are both called "lightweight Kubernetes," but their assumptions about datastores and OS update models are fundamentally different. We compare etcd lock-in and OSTree auto-rollback to help you choose for production edge deployments.
K3s vs MicroK8s: both are called 'lightweight Kubernetes,' but the real production divide is HA architecture. We compare K3s's embedded etcd and MicroK8s's dqlite using official documentation data.
A growing number of individuals are replacing ISP-supplied routers with self-built mini PCs running open-source firmware. The same logic applies to edge Kubernetes: a hardware selection checklist and a GitOps operating model for standardizing dedicated appliances out of the fleet.
When you can't rely on a cloud load balancer for on-prem or edge K3s clusters, why does Layer2 (ARP) load balancing eventually hit a wall? A practical look at MetalLB's BGP mode vs. Cilium's BGP Control Plane, and how to decide when to migrate.
Fleet management for K3s edge operations breaks down once you're troubleshooting devices one at a time by hand. Here's how declarative management and Rancher Fleet let you design edge operations that don't depend on any single person.
A field report from a large-scale K3s edge deployment covering 2,000+ devices: why lightweight Kubernetes gets chosen, and the hidden network cost of push-based metrics collection in a hybrid cluster architecture, backed by concrete numbers. For engineers and platform operators.
The trial-and-error troubleshooting behind a home-lab wall-mounted dashboard is the same trap that hits edge Kubernetes clusters scattered across factories and stores. Drawing on official K3s, Prometheus, and Grafana docs, this piece lays out design principles for not deferring observability.
Learn how to deploy K3s to edge and IoT environments. Covers Raspberry Pi setup, air-gapped installations, fleet management, and industry use cases.