-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support Service Account Impersonation #392
Comments
I think we should hold off on this until there's compelling user interest. Closing for now. |
@enocom Answering question from here. Our use case is we have a pod that needs access to GCP services such as Cloud Storage. This same pod also needs to access Cloud SQL. We access Cloud SQL via an IAM user added as a user on the instance. We don't want to add the pod service account as an IAM user on the Cloud SQL instance but prefer to access via service account impersonation. This is so we can maintain simplicity at the Postgres level itself by only managing one user but can grant access to the Cloud SQL instance by granting impersonation rights to other acting service accounts. |
Sounds totally legitimate. Thanks for the info. We'll get this feature merged. |
Now users can configure the proxy's --service-account-impersonation parameter. Fixes #392
Add support for configuring the proxy's Service Account Impersonation flag --impersonate-service-account
The text was updated successfully, but these errors were encountered: