e54d581ef5
Worker (hermes-agent) was hard-pinned to titan-08 (a workaround after an earlier attempt to place it on the amd64 titan-22 failed on architecture). That single- node pin is exactly what makes it fragile: a titan-08 blip (as just happened when the node's Longhorn CSI went down) strands worker, and the Recreate strategy then deadlocks because the replacement can't schedule on the one tight node. Restore the intended multi-node design: run on any arm64 storage worker except the known-bad/weak ones (matching the repo's own affinity test, which was red). Its Longhorn volumes have data-locality disabled with replicas on titan-15/17/19, so there is no locality penalty to running on another node; the scheduler now places it on a roomier Pi (e.g. titan-05) and a node blip simply reschedules it. Also relax the gateway /api/status liveness probe (timeout 10s->15s, failureThreshold 3->5) so a transient slowness (e.g. a brief storage hiccup) no longer trips a kill-and-restart cascade. Follow-up (separate): multi-arch agent image to enable the amd64 titan-22 target. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BvMSXH8VH2tMWXanb8SJdf
titan-iac
Flux-managed Kubernetes desired-state config for bstein.dev.
Canonical source URL:
ssh://git@scm.bstein.dev:2242/atlas/titan-iac.git
Scope
This repo contains cluster configuration consumed by Flux:
- platform/infrastructure manifests
- service manifests and kustomizations
- operational scripts for render/reconcile workflows
Apply model
I use Git + Flux as the source of truth and avoid manual in-cluster edits for durable changes.