4fe4162dad
Some checks failed
Tests / Declarative: Post Actions testing.tests.test_repo_structure.test_knowledge_service_mirror_matches_source failed
Several stages assumed the fixture job. On a code-demo run they would have read the fixture ConfigMap, which is unrelated to that job, and asserted that a field changing from unhealthy to healthy was the repair - flatly false when the outcome is a pull request. The route stage would also have claimed the source-proposal branch was not taken during the run that takes it. The stages now branch on the job: the route explains that a source fix is not a registered action and so takes the proposal branch; the response points at the pull request recorded on the incident; and the verify stage says the branch build validates the proposal and that nothing merges without a human whatever it reports. 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.