From 4a3ca572e8ec3ce9db5c0d7f1f200db62da83772 Mon Sep 17 00:00:00 2001 From: Viktor Barzin Date: Sun, 10 May 2026 13:09:15 +0000 Subject: [PATCH] fire-planner: imagePullPolicy=Always on alembic-migrate init container MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit After a rollout-restart, the main container (default Always for :latest) pulled the new image with alembic 0003, but the init container defaulted to IfNotPresent and reused a cached old image lacking 0003 → "Can't locate revision identified by '0003'" → CrashLoopBackOff. Setting Always on the init container so both containers stay in lockstep across rollouts. Longer term we should switch the deployment to 8-char git-SHA tags per the cluster policy in .claude/CLAUDE.md, but this unblocks the Wave 1 deploy in the meantime. --- stacks/fire-planner/main.tf | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/stacks/fire-planner/main.tf b/stacks/fire-planner/main.tf index b84cdc2b..c0b1f831 100644 --- a/stacks/fire-planner/main.tf +++ b/stacks/fire-planner/main.tf @@ -230,9 +230,10 @@ resource "kubernetes_deployment" "fire_planner" { } init_container { - name = "alembic-migrate" - image = local.image - command = ["python", "-m", "fire_planner", "migrate"] + name = "alembic-migrate" + image = local.image + image_pull_policy = "Always" + command = ["python", "-m", "fire_planner", "migrate"] env_from { secret_ref {