# Schema migrator not given sidecar containers

**URL:** <https://community.temporal.io/t/schema-migrator-not-given-sidecar-containers/15752>\
**Category:** Server Deployment\
**Created:** [December 18, 2024, 2:53pm UTC](https://community.temporal.io/t/schema-migrator-not-given-sidecar-containers/15752 "2024-12-18T14:53:27Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Andrew\_Stevens](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/andrew_stevens/32/6514_2.png) [@Andrew\_Stevens](https://community.temporal.io/u/Andrew_Stevens)\
**Post date:** [December 18, 2024, 2:53pm UTC](https://community.temporal.io/t/schema-migrator-not-given-sidecar-containers/15752/1 "2024-12-18T14:53:27Z")

</div>

Hi!

I didn’t find a _ton_ of documentation about it, but when deploying via helm it looks like there is an option to run DB schema initialization/migration. See config options here:

> <https://github.com/temporalio/helm-charts/blob/34e5abb2dc2ec149124f633bade5e8503b94b23e/charts/temporal/values/values.postgresql.yaml#L76>

I tried enabling these, and the jobs were created but failed. I believe the reason is that we’re using Google’s Cloud SQL Proxy to connect to our Postgres instance (per the example [here](https://github.com/temporalio/helm-charts/blob/main/charts/temporal/values/values.cloudsqlproxy.yaml), which works OK for the main temporal services. However I don’t think the sidecar containers are being configured for the schema migrator job.

Does this sound correct? And is this a bug?

Thanks!  
Andrew