137ea77e95
The fixture check waited on the Job's .status.succeeded/.status.failed. The kubelet records a container's exit code the instant it stops, but the Job controller reconciles those fields on its own schedule: observed at 2m24s, 4m27s and 34m on this cluster for identical work. During that window the pod had already exited 1 and the build sat printing 'Will try again after 13 sec', looking hung long after the test had finished, which is unusable in a demo. Polling the pod's terminated exitCode removes the controller from the path entirely. The Job is still used, so the evidence shape is unchanged. 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.