[google-cloud-sql-discuss] Kubernetes Proxy Sidecar One per pod or behind service?

The documentation for how to connect to CloudSQL from Kubernetes is to add a sidecar pod. 

We have many different types of deployments that require database connection does it make sense to expose the proxy via a service running in a separate single deployment? 

Further, it suggests creating a proxyuser. It seems I should continue using the username/password as I've always used instead of creating one specific to a proxy. Any more information I'm missing here?

Thanks!

Joe

--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/5a7fe2f1-9d97-4848-93e5-fdb35643e903%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.