cloud-sql-proxy

Is it possible to replace Cloud SQL proxy with Istio proxy?

由 感情迁移 提交于 2021-01-01 06:53:24
问题 Currently I am using Cloud proxy to connect to a Postgres Cloud SQL database as a sidecar. When using Istio, however it introduces its own sidecar, which lead to the result that there are two proxies in the pod. So I thougth, can the encrypted connection not also established using Istio? Basically, it is possible to connect to an external IP using Istio. It should also be possible to configure a DestinationRule which configures TLS. And it also be possible to create Client certificates for

Control order of container termination in a single pod in Kubernetes

由 限于喜欢 提交于 2020-05-25 05:13:28
问题 I have two containers inside one pod. One is my application container and the second is a CloudSQL proxy container. Basically my application container is dependent on this CloudSQL container. The problem is that when a pod is terminated, the CloudSQL proxy container is terminated first and only after some seconds my application container is terminated. So, before my container is terminated, it keeps sending requests to the CloudSQL container, resulting in errors: could not connect to server:

Control order of container termination in a single pod in Kubernetes

由 生来就可爱ヽ(ⅴ＜●) 提交于 2020-05-25 05:12:52
问题 I have two containers inside one pod. One is my application container and the second is a CloudSQL proxy container. Basically my application container is dependent on this CloudSQL container. The problem is that when a pod is terminated, the CloudSQL proxy container is terminated first and only after some seconds my application container is terminated. So, before my container is terminated, it keeps sending requests to the CloudSQL container, resulting in errors: could not connect to server:

“new ephemeral certificate expires too soon: current time:”M

由 China☆狼群 提交于 2020-02-25 13:28:49
问题 I've been connecting to Google Cloud Platform MySQL from the CloudSQL Proxy on Windows for years. All of a sudden, I'm unable to connect. When I start the proxy using PowerShell, it launches fine and says ready for new connections. Then when I try to connect to it on 127.0.0.1, the client will report back: "Lost connection to MySQL server during query (127.0.0.1:3306)" The CloudSQL Proxy will report in the terminal: "error: new ephemeral certificate expires too soon: current time: 2019-06-28

Connecting to multiple CloudSQL instances using Cloud sql proxy?

由 只愿长相守 提交于 2019-12-19 17:44:50
问题 I'm attempting to use the cloud sql proxy to connect to 2 different cloud sql instances... In the docs I found a line about Use -instances parameter. For multiple instances, use a comma-separated list. but not sure how to make that look. https://cloud.google.com/sql/docs/sql-proxy. I'm using Google Container engine, and with a single CloudSQL instance it works great: - name: cloudsql-proxy image: b.gcr.io/cloudsql-docker/gce-proxy:1.05 command: ["/cloud_sql_proxy", "--dir=/cloudsql", "

Start CloudSQL Proxy on Python Dataflow / Apache Beam

由 可紊 提交于 2019-12-18 17:01:49
问题 I am currently working on a ETL Dataflow job (using the Apache Beam Python SDK) which queries data from CloudSQL (with psycopg2 and a custom ParDo ) and writes it to BigQuery. My goal is to create a Dataflow template which I can start from a AppEngine using a Cron job. I have a version which works locally using the DirectRunner. For that I use the CloudSQL (Postgres) proxy client so that I can connect to the database on 127.0.0.1 . When using the DataflowRunner with custom commands to start

Google cloud dataproc failing to create new cluster with initialization scripts

由 ε祈祈猫儿з 提交于 2019-12-13 07:37:30
问题 I am using the below command to create data proc cluster: gcloud dataproc clusters create informetis-dev --initialization-actions “gs://dataproc-initialization-actions/jupyter/jupyter.sh,gs://dataproc-initialization-actions/cloud-sql-proxy/cloud-sql-proxy.sh,gs://dataproc-initialization-actions/hue/hue.sh,gs://dataproc-initialization-actions/ipython-notebook/ipython.sh,gs://dataproc-initialization-actions/tez/tez.sh,gs://dataproc-initialization-actions/oozie/oozie.sh,gs://dataproc

cannot fetch token error when using cloudsql-proxy with GKE

由 狂风中的少年 提交于 2019-12-10 09:31:38
问题 I am using GKE with istio add-on enabled. Myapp somehow gives 503 errors using when using websocket. I am starting to think that maybe the websocket is working but the database connection is not and that causes 503's, as the cloudsql-proxy logs give errors: $ kubectl logs myapp-54d6696fb4-bmp5m cloudsql-proxy 2019/01/04 21:56:47 using credential file for authentication; email=proxy-user@myproject.iam.gserviceaccount.com 2019/01/04 21:56:47 Listening on 127.0.0.1:5432 for myproject:europe

no connection pool with primary found

由 若如初见. 提交于 2019-12-10 03:36:41
问题 I am using Rails and am experiencing a connection pool error very randomly and it does not target any single endpoint specifically. I can hit endpoints about 70% of the time without getting this error. The database is PostgreSQL running on Google Cloud. Here's the main stuff of the error I'm getting: #<ActiveRecord::ConnectionNotEstablished: ActiveRecord::ConnectionNotEstablished> /usr/local/bundle/gems/activerecord-5.1.5/lib/active_record/connection_handling.rb:112:in `connection_pool'

cannot fetch token error when using cloudsql-proxy with GKE

由 戏子无情 提交于 2019-12-05 13:41:16
I am using GKE with istio add-on enabled. Myapp somehow gives 503 errors using when using websocket. I am starting to think that maybe the websocket is working but the database connection is not and that causes 503's, as the cloudsql-proxy logs give errors: $ kubectl logs myapp-54d6696fb4-bmp5m cloudsql-proxy 2019/01/04 21:56:47 using credential file for authentication; email=proxy-user@myproject.iam.gserviceaccount.com 2019/01/04 21:56:47 Listening on 127.0.0.1:5432 for myproject:europe-west4:mydatabase 2019/01/04 21:56:47 Ready for new connections 2019/01/04 21:56:51 New connection for
订阅 cloud-sql-proxy