chore(fleet): retire lazer-machine from the fleet health board #196

Merged

kblack0610 merged 1 commit from chore/fleet-remove-lazer-machine into master

2026-08-17 18:36:56 +00:00

kblack0610 commented

2026-08-17 18:35:24 +00:00

Owner

The Deloitte contract ended, so the VDI is gone. Its last heartbeat to fleet.kblab.me was 2026-08-15T22:01Z - already stale, and gatus has no server-side expiry, so a retired machine left declared pins the fleet glyph amber forever (the trap that got the sleeping iot Pi Zeros removed).

Dropped from both in-repo denominators in lockstep:

apps/gatus-fleet/config.yaml - the workplace external-endpoint
apps/fleet-exporter/deployment.yaml - FLEET_ROSTER

The third denominator (FLEET_ROSTER in ~/.config/fleet-pulse/env) lives in the ~/.dotfiles-private overlay and ships as its own PR: chore/fleet-retire-lazer-machine.

README gains a Retiring a machine section listing all three places, since drift between them is what fleet_machine_unrostered exists to catch.

Verified: kubectl kustomize apps/gatus-fleet and apps/fleet-exporter both build with no lazer-machine endpoint or roster entry (only an explanatory comment remains).

Out of scope: the Lazer routes in apps/litellm - flagged separately.

The Deloitte contract ended, so the VDI is gone. Its last heartbeat to fleet.kblab.me was `2026-08-15T22:01Z` - already stale, and gatus has no server-side expiry, so a retired machine left declared pins the fleet glyph amber forever (the trap that got the sleeping iot Pi Zeros removed). Dropped from both in-repo denominators in lockstep: - `apps/gatus-fleet/config.yaml` - the `workplace` external-endpoint - `apps/fleet-exporter/deployment.yaml` - `FLEET_ROSTER` The third denominator (`FLEET_ROSTER` in `~/.config/fleet-pulse/env`) lives in the `~/.dotfiles-private` overlay and ships as its own PR: `chore/fleet-retire-lazer-machine`. README gains a **Retiring a machine** section listing all three places, since drift between them is what `fleet_machine_unrostered` exists to catch. Verified: `kubectl kustomize apps/gatus-fleet` and `apps/fleet-exporter` both build with no `lazer-machine` endpoint or roster entry (only an explanatory comment remains). Out of scope: the Lazer routes in `apps/litellm` - flagged separately.

kblack0610 added 1 commit

2026-08-17 18:35:25 +00:00

chore(fleet): retire lazer-machine from the fleet health board f141d8a906

The Deloitte contract ended, so the VDI is gone. Its last heartbeat to
fleet.kblab.me was 2026-08-15T22:01Z - a retired machine left declared is
worse than absent, because gatus has no server-side expiry and the stale
row pins the fleet glyph amber forever (the same false-signal trap that
got the sleeping iot Pi Zeros removed).

Dropped in lockstep from both denominators so they cannot drift:
- apps/gatus-fleet/config.yaml     - the external-endpoint itself
- apps/fleet-exporter/deployment.yaml - FLEET_ROSTER (Grafana/Prometheus)

The third denominator, FLEET_ROSTER in ~/.config/fleet-pulse/env, lives in
the ~/.dotfiles-private overlay and ships as its own PR.

README gains a "Retiring a machine" section with all three places, since
the drift between them is what fleet_machine_unrostered exists to catch.