Each k3s node in the Bluespeed fleet has a hostname and an optional reset number stored as a k8s node label (bluespeed/resets). The number is a visual easter egg — it goes up when a contributor confirms their fix landed in Bluefin. No automation, no tracking, honor system only.
When a contributor runs ujust exo-reset, the CLI tells them they've earned a rest and patches the node label. That's the whole feature.
Two additional custom labels per node: bluespeed/display-name and bluespeed/description. User sets these at node enrollment. The cluster is the registry — no separate YAML file.
CNCF context: k8s node labels are the native metadata store. No external registry. No database.
Principle: Lore lives in docs only. Tech is standard Linux/k8s naming. ujust exo-reset is the only surface where the easter egg shows up.
Each k3s node in the Bluespeed fleet has a hostname and an optional reset number stored as a k8s node label (
bluespeed/resets). The number is a visual easter egg — it goes up when a contributor confirms their fix landed in Bluefin. No automation, no tracking, honor system only.When a contributor runs
ujust exo-reset, the CLI tells them they've earned a rest and patches the node label. That's the whole feature.Two additional custom labels per node:
bluespeed/display-nameandbluespeed/description. User sets these at node enrollment. The cluster is the registry — no separate YAML file.CNCF context: k8s node labels are the native metadata store. No external registry. No database.
Principle: Lore lives in docs only. Tech is standard Linux/k8s naming.
ujust exo-resetis the only surface where the easter egg shows up.