Install temporal with helm chart configured with sql/Postgres persistent storage
Describe the bug
Configured helm values file using example for Postgres. After running helm deploy noticed that container for temporal-schema-setup is in a crash loop. Logs say cannot connect to database <>. Database does not exist
Looking at the helm chart, noticed that in server-job.yaml a create-default-store and create-visibility-store init containers should be created.
Generated complete manifest with helm template -f my_values.yaml . and noticed that initContainers section is empty (contains [] only)
Minimal Reproduction
Using example values file for Postgres, generate deployment manifests with:
What are you really trying to do?
Install temporal with helm chart configured with sql/Postgres persistent storage
Describe the bug
Configured helm values file using example for Postgres. After running helm deploy noticed that container for
temporal-schema-setup
is in a crash loop. Logs saycannot connect to database <>. Database does not exist
Looking at the helm chart, noticed that in server-job.yaml a
create-default-store
andcreate-visibility-store
init containers should be created.Generated complete manifest with
helm template -f my_values.yaml .
and noticed thatinitContainers
section is empty (contains[]
only)Minimal Reproduction
Using example values file for Postgres, generate deployment manifests with:
Inspect section
# Source: temporal/templates/server-job.yaml
which shows noinitContainers
were generatedEnvironment/Versions
Additional context
This bug was introduced with new Helm release when
Values.schema.createDatabase.enabled
variable was added: https://github.com/temporalio/helm-charts/commit/f6e0e3aae1b4df067526d989d2e2e86e8c4e1490