Describe the problem
Currently, the chart only supports static credentials. I’d like to be able to provide a GCP service account so that the pod can authenticate through the existing proxy.
I already run a Cloud SQL Auth Proxy locally via sidecar in the pod, and could connect via psql:
psql -h <db_adress> -p <db_port> -U <iam_account> <database>"
Solution brainstorm
Allow Weblate Helm chart to connect to a Cloud SQL PostgreSQL instance via IAM authentication using an existing Cloud SQL Auth Proxy, without requiring username/password in the chart.
Maybe add as redis, add postgresql.auth.enabled: false in order to use only username/adress/port ?
Describe alternatives you have considered
No response
Screenshots
No response
Additional context
No response
Describe the problem
Currently, the chart only supports static credentials. I’d like to be able to provide a GCP service account so that the pod can authenticate through the existing proxy.
I already run a Cloud SQL Auth Proxy locally via sidecar in the pod, and could connect via psql:
psql -h <db_adress> -p <db_port> -U <iam_account> <database>"Solution brainstorm
Allow Weblate Helm chart to connect to a Cloud SQL PostgreSQL instance via IAM authentication using an existing Cloud SQL Auth Proxy, without requiring username/password in the chart.
Maybe add as redis, add
postgresql.auth.enabled: falsein order to use only username/adress/port ?Describe alternatives you have considered
No response
Screenshots
No response
Additional context
No response