Requiring rpi5 while the historical hostname exclusion list removes the very rpi5 nodes that currently have headroom (titan-04/06) left only loaded rpi5s (titan-05/07/11), so the agent could not schedule and worker went down. Revert to rpi5-PREFERRED (soft) so it schedules again; proper rpi5 placement needs the exclusion list refreshed against current node health/capacity, tracked separately. 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.
Description
Languages
Python
74.6%
JavaScript
10.2%
Shell
6.1%
TypeScript
3.7%
Go
2%
Other
3.2%