Support GCP service account for IAM auth with existing Cloud SQL Proxy
Nobody has claimed this yet.
- Dominant language
- Mustache
- Stars
- 41
- Forks
- 45
- Avg merge
- 1h 24m
- Merged PRs (30d)
- 37
Description
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
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Helm chart configuration for PostgreSQL static credentials and compare it with the existing Redis authentication options. Reproduce the described psql connection through an existing Cloud SQL Auth Proxy, then define completion as connecting to Cloud SQL PostgreSQL with a GCP service account without requiring username/password credentials in the chart.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- gcp, helm, postgresql
- Domain
- authentication, cloud, databases, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100