infra/stacks/t3-afk
Viktor Barzin 82a0c5aedf
All checks were successful
ci/woodpecker/push/default Pipeline was successful
t3-afk: fix crashloop — exclude from Keel at the deployment level
Keel "patch"-downgraded the image docker.io/library/node:24 -> library/node:24.0.2,
which is below t3@0.0.27's required node >=24.10, so `t3 serve` exited silently and
the pod crash-looped (~160 restarts / 13h).

Root cause: keel.sh/policy=never was on the POD-TEMPLATE labels, but Keel reads the
policy at the DEPLOYMENT level. The cluster's Kyverno inject-keel-annotations is
opt-out, so it stamped policy=patch and Keel acted on it.

Fix: set keel.sh/policy=never as a deployment-level annotation; ignore_changes the
Kyverno-injected keel.sh/pollSchedule + keel.sh/trigger annotations; the image stays
TF-owned (apply reverted Keel's downgrade). Pod now 1/1, t3 serve 200.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-15 10:32:38 +00:00
..
files t3-afk: dedicated in-cluster T3 Code instance (AFK executor + cockpit) 2026-06-14 20:06:33 +00:00
main.tf t3-afk: fix crashloop — exclude from Keel at the deployment level 2026-06-15 10:32:38 +00:00
terragrunt.hcl t3-afk: dedicated in-cluster T3 Code instance (AFK executor + cockpit) 2026-06-14 20:06:33 +00:00