Schema migrator not given sidecar containers

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:

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, 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