Bluespeed's first and primary use case: make it trivially easy for any Bluefin contributor or user to run local hardware testing, send reports back, and have Hive triage the results.
The loop:
- Contributor runs
ujust report — collects device info, stores in their own gist (user-controlled, never leaves their hands without consent)
- Hive triages incoming reports as issues
- Contributors can locally confirm a PR fix on their own hardware
- Anyone with a laptop can participate — no homelab required
Why this is p0: This accelerates Bluefin contributions immensely. It closes the gap between "something is broken on my machine" and "here is a reproducible report with a confirmed fix." The entire Bluespeed platform exists to serve this loop.
The platform: Flatcar + k3s + KubeStellar Console + Argo Workflows — all deployed via just setup on a single control box. The dashboard (Bluespeed) shows fleet health, cluster state, and contributor activity. Clients are laptops running bootc images — not k3s nodes.
CNCF context: OTel Collector (incubating) ships telemetry. Prometheus (graduated) stores metrics. bootc (sandbox) manages OS updates. Argo Workflows (graduated) runs build pipelines. k3s is the distribution.
Key constraint: Laptops are clients that consume bootc images — they are never k3s nodes. Enrollment = OTel agent installation only.
Bluespeed's first and primary use case: make it trivially easy for any Bluefin contributor or user to run local hardware testing, send reports back, and have Hive triage the results.
The loop:
ujust report— collects device info, stores in their own gist (user-controlled, never leaves their hands without consent)Why this is p0: This accelerates Bluefin contributions immensely. It closes the gap between "something is broken on my machine" and "here is a reproducible report with a confirmed fix." The entire Bluespeed platform exists to serve this loop.
The platform: Flatcar + k3s + KubeStellar Console + Argo Workflows — all deployed via
just setupon a single control box. The dashboard (Bluespeed) shows fleet health, cluster state, and contributor activity. Clients are laptops running bootc images — not k3s nodes.CNCF context: OTel Collector (incubating) ships telemetry. Prometheus (graduated) stores metrics. bootc (sandbox) manages OS updates. Argo Workflows (graduated) runs build pipelines. k3s is the distribution.
Key constraint: Laptops are clients that consume bootc images — they are never k3s nodes. Enrollment = OTel agent installation only.