c44f16e4ac
Un-pinning let the scheduler land worker on titan-12 (rpi4). The agent is heavy enough that an rpi4 risks the /api/status slowness that trips its liveness probe - the exact flap we are avoiding. Make hardware=rpi5 a hard requirement so it runs only on rpi5 storage workers (excluding the saturated/known-flaky ones); the scheduler places it on a roomy rpi5 (titan-05). 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.