Skip to content

feat: add setupJob.enabled to gate the setup Job - #632

Open
bstanforth-mitek wants to merge 1 commit into
zitadel:mainfrom
bstanforth-mitek:feat/setupJob-enabled
Open

bstanforth-mitek wants to merge 1 commit into
zitadel:mainfrom
bstanforth-mitek:feat/setupJob-enabled

Conversation

@bstanforth-mitek

@bstanforth-mitek bstanforth-mitek commented Oct 27, 2026 •

Copy link
Copy Markdown

Summary

Adds setupJob.enabled (default true) mirroring initJob.enabled, so operators can omit the setup Job on secondary clusters that share one Postgres with a primary that already runs migrations / FirstInstance.

zitadel.configmapConfig.FirstInstance.Skip only skips FirstInstance provisioning inside setup; it does not skip migrations or remove the Job. Concurrent setup Jobs against a shared DB can race non-idempotent DDL (e.g. 07_logstore / protocol_date_desc already exists).

Changes

  • Wrap templates/job_setup.yaml with {{- if .Values.setupJob.enabled }}
  • Document setupJob.enabled in values.yaml and values.schema.json

Test plan

  • helm template with setupJob.enabled: true still emits the setup Job
  • helm template with setupJob.enabled: false emits no *-setup Job
  • initJob / Deployment / login templates unchanged

Mirror initJob.enabled so multi-region deployments that share one Postgres
can disable setup (migrations + FirstInstance) on secondary clusters.
FirstInstance.Skip alone does not omit the Job or skip migrations.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant