2bfdee6169
titan-24 is an accelerator node (co-hosts the out-of-cluster Sui validator), not a general worker. The amd64 build leg was requiring node-role worker=true, which forced labeling titan-24 as a worker and opened it to unrelated cluster scheduling. It already pins by hostname+arch, so drop the worker requirement and remove the titan-24 worker-join from the node-prefer CronJob entirely. The build targets titan-24 specifically (hostname) and tolerates its taint; nothing else in the cluster gets scheduled there. 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.