Fleet management

Running k3s across a hundred sites with intermittent connectivity — and the test almost nobody applies to their own architecture, which is whether someone else can take it over.

Draft

This page is seeded structure, not finished writing. The author has not rewritten it yet.

One cluster is a tutorial. A hundred clusters in a hundred buildings, half of them behind a firewall an OT team controls, is a different discipline.

Intermittent is the normal case

Designing for a link that is usually up is how you build something that fails badly. Reconciliation has to be the default behaviour, not the recovery path.

The commissioning window

Line commissioning is when infrastructure decisions get made under time pressure by people who will never touch them again. What you ship has to survive that.

Resource budgets are a design constraint

If it needs a datacenter, it does not belong at the edge. What that rules out, and what it forces you to do better.

We built the fleet. Another supplier runs it now. Reversibility is not a licensing claim, it is whether the next team can actually take over — and most architectures fail this test the first time it is applied.

Writing on this

Guide

Kubernetes 101

What Kubernetes is, what problems it solves, and how it is composed and start using it.

Related work

Start-Alpha

One blueprint to deploy, govern and recover distributed infrastructure — from edge to cloud. Secure software supply-chain, from OS to applications.

k3s