Hello all, i am trying to deploy airbyte in a managed kubernetes cluster via your provided helm chart. I am using an external Postgres and instead of minio i am using s3 directly. After the bootloader finishes, only the metrics and the cron pod start successfully. The other pods run into a CrashLoopBackOff. I think the root cause of the other pods not starting is, that the temporal pod terminates with this line in the log

unable to create open /etc/temporal/config/docker.yaml: permission denied

. Does anyone can help me out here? I am not able to run the pods privilaged, since it is not allowed in my cluster. In a local minikube environment everything started properly with my supplied values.yaml. Thank you in advance!

might also be related to this: https://discuss.airbyte.io/t/worker-process-of-airbyte-v0-40-9-fails-to-start-on-custom-s3-config/2849

I was able to make it work by extending the temporalio:auto-setup and add a user.