From 6ebecec1c48ecd86528ac1b2f522a51147853254 Mon Sep 17 00:00:00 2001
From: pi <pi@local>
Date: Sun, 25 Oct 2026 09:47:33 -0700
Subject: [PATCH] fix(zitadel): raise setup job deadline to 20m

The chart default killed zitadel-setup at ~5.5 minutes while it was still
replaying projections.projects4, which failed the whole PreSync and left the
Application OutOfSync/Missing. 1200s leaves room for a cold database without
masking a genuine hang.
---
 k8s/infra/iam/zitadel-values.yaml | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/k8s/infra/iam/zitadel-values.yaml b/k8s/infra/iam/zitadel-values.yaml
index b3e3dbc..d5b15eb 100644
--- a/k8s/infra/iam/zitadel-values.yaml
+++ b/k8s/infra/iam/zitadel-values.yaml
@@ -88,6 +88,14 @@ initJob:
   command: "zitadel"
   activeDeadlineSeconds: 600
 
+# The setup job runs the full first-instance creation: schema migrations, the
+# system org, the iam-admin machine key, and 13 projection replays. The chart
+# default killed it at ~5.5 minutes on 2026-10-25 while it was still replaying
+# projections.projects4, which failed the whole sync. 20 minutes leaves room for
+# a cold database without masking a genuine hang.
+setupJob:
+  activeDeadlineSeconds: 1200
+
 # Two API replicas: the read path survives one node drain, and both share the
 # same masterkey and database. The login UI stays at one replica — a session
 # cookie is not shared, so a second pod buys nothing.