e3e40f4618
Every human_required escalation already files an issue in the failing service's own repository, and mailing on each one made the inbox the loudest and least informative output of the system. Replace the blanket alert with two narrow ones: a repair that ran and failed, which is the only case where the automation acted and left things no better, and an escalation still untouched after six hours. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
titan-iac
Flux-managed Kubernetes desired-state config for bstein.dev.
Canonical source URL:
ssh://git@scm.bstein.dev:2242/bstein/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.