Jobs are timed out when using extra container with cloud-sql-proxy
Hey, I am having an issue with installing this Helm chart and using a Cloud SQL database.
I have set up an extra container with cloud-sql-proxy, basically just uncommented the section that was there.
The problem is that extra container keeps working after the init script in the main container has finished so the whole job is considered to be running. After this {{ .Values.initJob.activeDeadlineSeconds }} amount of time the job is being killed and failed. The installation process doesn't go any further
Run helm install
Either Init (if it's enabled) or setup job will fail because of activeDeadlineSeconds
Am I doing something wrong? Did anyone run into that?
Thank you.
P.S.
I opened an issue here as well https://github.com/zitadel/zitadel-charts/issues/344
I have set up an extra container with cloud-sql-proxy, basically just uncommented the section that was there.
The problem is that extra container keeps working after the init script in the main container has finished so the whole job is considered to be running. After this {{ .Values.initJob.activeDeadlineSeconds }} amount of time the job is being killed and failed. The installation process doesn't go any further
To reproduce
Specify extraContainers with some process that is running infinitelyRun helm install
Either Init (if it's enabled) or setup job will fail because of activeDeadlineSeconds
Logs
Am I doing something wrong? Did anyone run into that?
Thank you.
P.S.
I opened an issue here as well https://github.com/zitadel/zitadel-charts/issues/344
