16d771aa69
An audience watching a dashboard has to take the result on trust. Watching kubectl run against the cluster and reading the raw answer is the difference between a demonstration and an assertion, so every read is now printed before it runs and its output shown beneath. Each stage also names the service UI worth looking at when something changes there: the Jenkins job as the build goes red and again when the rebuild starts on its own, the Hermes dashboard as the agent run appears, the Grafana triage panels and the filed issues at the end. 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.