Saturday, May 19, 2018

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

Hello Joe,


Following this tutorial, the container containing your application, and the Cloud SQL proxy container (sidecar) should be tightly coupled in a single manageable entity (Pod) per your deployment (wordpress example), and the same applies for each replica pod. This is the recommended method to use with Kubernetes. But, I am not sure if it would be ideal for your use case. That said, and as you mentioned you may test  deploying Cloud SQL proxy as a cluster service using Helm per this Github example


To answer your last question about the username, the tutorial for clarity reasons, and for easier cleanup ( when you finish the example) suggests to create a new username. It is not necessary if you already have a username/password you plan to use. I hope that helps.


--
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/ff2a197a-1bc7-40a4-b2ed-d8d9bb25e813%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

No comments:

Post a Comment