viktor/infra
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

fire-planner: imagePullPolicy=Always on alembic-migrate init container

Browse source 
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.
This commit is contained in:
Viktor Barzin 2026-05-10 13:09:15 +00:00
parent 67b11a964a
commit 4a3ca572e8
1 changed files with 4 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

7
stacks/fire-planner/main.tf
View file

@ -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 {