approvedcompleteAGPL-3.0
Fleet: deployd's core as an in-process addon, placing EnRaHiTu apps
006-fleet
Milestone M3: operate stamped apps. The unit of placement is "one EnRaHiTu container + one volume + one ingress" on the existing hetzner-k3s cluster. deployd-api-rs (the OAP-era Rust K8s orchestrator, axum + hiqlite) donates its orchestration core as a napi-rs addon (the hiqlite-native pattern): the axum HTTP layer disappears, the K8s knowledge stays. A fleet/ Encore service exposes deploy / status / update / backup over the addon. Done-when is a fleet of ten stamped apps on one box with update and backup exercised.
- Depends on
- Establishes
- backend/fleet/ (directory)
- addon/fleet-native/ (directory)
- Sections
- 006: Fleet
- 1. Source of the K8s knowledge (reference, not a port)
- 2. Territory
- 3. Behavior
- 4. Acceptance
- Status (2026-07-15)
- Live E2E attempt 2026-07-15 (first real deploy on hetzner-k3s)
- 2026-07-16: code fixes #2/#3 landed; live E2E still blocked on external state
- 2026-07-16 (later): live E2E passed on deployd.xyz; 006 complete
- 5. Out of scope
- Source
- specs/006-fleet/spec.md @ 3e93e94f770bas of 2026-07-17 ยท shard bfeee366bfd9