Flight log
19 of 43 issues closed (44%). 9 joined after takeoff. Stretch: 7 of 21.
Rebuilt whenever an issue changes. Last update: 2026-11-18 21:09 UTC.
Leg 0 · The bench
landed, due 2026-11-12
- #40 Release versioned increments and publish them from CI (landed 2026-11-13)
- #37 Decide on just, mise and a local registry (landed 2026-11-13)
- #2 Scaffold the workspace and CI (landed 2026-11-12)
- #1 Install the bench tools (landed 2026-11-12)
- #44 Show build health and assurance badges in the README (landed 2026-11-12)
- #39 Track progress with a flight strip (landed 2026-11-12)
- #38 Check every push for secrets and blocked terms (landed 2026-11-12)
- #35 Publish the docs site and keep it current (landed 2026-11-12)
Leg 1 · A cluster I built myself
in flight, due 2026-11-20
- #14 Run Redpanda on local storage (landed 2026-11-18)
- #13 Drill: snapshot and restore etcd (landed 2026-11-17)
- #12 Drill: lose one control plane, then two (landed 2026-11-17)
- #105 Bootstrap the cluster with one command (landed 2026-11-15)
- #11 Bootstrap a highly available control plane by hand (landed 2026-11-15)
- #82 Mirror quay.io and ghcr.io on the host, so Cilium and kube-vip pull once (landed 2026-11-14)
- #75 Cache packages and images on the host, so a rebuild doesn't refetch them (landed 2026-11-14)
- #10 Build five VMs with cloud-init (landed 2026-11-14)
- #15 Run ClickHouse with raw, deduplicated and rolled-up tables
- #16 Decide on kubeadm and on Redpanda
- #17 Checkpoint: explain quorum, static Pods and MergeTree merges
Leg 2 · Firmware and the wire
started early, due 2026-11-24
- #3 Boot Embassy firmware on an STM32F4 in Renode (landed 2026-11-14)
- #62 Re-plan the route in evenings (landed 2026-11-14)
- #56 Keep a daily blog on the docs site (landed 2026-11-13)
- #4 Drive the control loop from a hardware timer at 1 kHz
- #5 Estimate attitude from a simulated IMU
- #6 Send MAVLink v2 telemetry over UART with DMA
- #7 Read the telemetry on the host with pymavlink
- #8 Decide on MAVLink v2 over a custom framing
- #9 Checkpoint: explain the firmware and the frame format
- #61 Test the firmware in Renode with Robot Framework
Leg 3 · Serial port to ClickHouse
not started, due 2026-11-30
- #18 Find MAVLink frames in a noisy byte stream
- #19 Publish frames to Redpanda without losing any
- #20 Run the gateway on the node that owns the serial link
- #21 Stream frames from Redpanda into ClickHouse with Spate
- #22 Route attitude, IMU and timing into their own tables
- #23 Fly end to end, from firmware to Grafana
- #24 Decide to deduplicate in ClickHouse over chasing exactly-once
- #25 Checkpoint: explain a frame's whole path
- #107 Deliver the workloads from Git with Flux
Leg 4 · Break it and prove it
not started, due 2026-12-04
- #26 Report gaps, duplicates and latency with bbcheck
- #27 Drill: break the pipeline while it streams
- #28 Build Grafana dashboards for the whole path
- #29 Finish the README and record a demo
- #30 Checkpoint: walk through the system and defend the decisions
Stretch
bonus
- #116 Run only the CI a change needs, and merge stacks in one go (landed 2026-11-17)
- #47 Scan the code with CodeQL (landed 2026-11-16)
- #46 Keep pinned actions current with Dependabot (landed 2026-11-16)
- #45 Choose a licence (landed 2026-11-16)
- #95 Draw how the flight tracker works (landed 2026-11-15)
- #90 Draw a narrow flight rack for phones (landed 2026-11-14)
- #86 Redraw the flight strip as a rack, one strip per leg (landed 2026-11-14)
- #31 Test firmware on the cluster from GitHub Actions
- #32 Write an Apache Iggy source for Spate
- #33 Add a CAN bus alongside MAVLink
- #34 Queue work by priority with Kueue
- #36 Stream metrics to a public Grafana dashboard
- #102 Serve the metrics API with verified kubelet certificates
- #124 Provision volumes on demand with local-path-provisioner
- #130 Rebuild the platform on Talos, OpenTofu and Flux
- #131 Decide on Talos, OpenTofu and Flux for the finished platform
- #132 Provision the VMs with OpenTofu on libvirt
- #133 Run Talos on the nodes
- #134 Run the host services from Compose
- #135 Move the cluster checks and etcd backups onto standard tools
- #136 Turn the checks into Chainsaw tests
How this page is drawn
The diagram is wide, so here it is full size.