From aa08dfd60fc8b7e31d18005b2312b111724ab5b4 Mon Sep 17 00:00:00 2001 From: Jack Wotherspoon Date: Wed, 22 Feb 2023 14:23:51 -0500 Subject: [PATCH] chore: update examples proxy version to v2.1.0 (#1674) --- examples/k8s-health-check/proxy_with_http_health_check.yaml | 2 +- examples/k8s-service/pgbouncer_deployment.yaml | 4 +++- examples/k8s-sidecar/proxy_with_sa_key.yaml | 2 +- examples/k8s-sidecar/proxy_with_workload_identity.yaml | 2 +- 4 files changed, 6 insertions(+), 4 deletions(-) diff --git a/examples/k8s-health-check/proxy_with_http_health_check.yaml b/examples/k8s-health-check/proxy_with_http_health_check.yaml index a72c573f5..928e4449a 100644 --- a/examples/k8s-health-check/proxy_with_http_health_check.yaml +++ b/examples/k8s-health-check/proxy_with_http_health_check.yaml @@ -49,7 +49,7 @@ spec: - name: cloud-sql-proxy # It is recommended to use the latest version of the Cloud SQL proxy # Make sure to update on a regular schedule! - image: gcr.io/cloud-sql-connectors/cloud-sql-proxy:2.0.0 # make sure to use the latest version + image: gcr.io/cloud-sql-connectors/cloud-sql-proxy:2.1.0 args: # If connecting from a VPC-native GKE cluster, you can use the # following flag to have the proxy connect over private IP diff --git a/examples/k8s-service/pgbouncer_deployment.yaml b/examples/k8s-service/pgbouncer_deployment.yaml index 40b951ee7..0e2970627 100644 --- a/examples/k8s-service/pgbouncer_deployment.yaml +++ b/examples/k8s-service/pgbouncer_deployment.yaml @@ -82,7 +82,9 @@ spec: - name: CLIENT_TLS_CERT_FILE value: "/etc/server/cert.pem" - name: cloud-sql-proxy - image: gcr.io/cloud-sql-connectors/cloud-sql-proxy:2.0.0 # make sure to use the latest version + # It is recommended to use the latest version of the Cloud SQL proxy + # Make sure to update on a regular schedule! + image: gcr.io/cloud-sql-connectors/cloud-sql-proxy:2.1.0 args: - "--port=5431" - "" diff --git a/examples/k8s-sidecar/proxy_with_sa_key.yaml b/examples/k8s-sidecar/proxy_with_sa_key.yaml index ab8301032..160b69a9a 100644 --- a/examples/k8s-sidecar/proxy_with_sa_key.yaml +++ b/examples/k8s-sidecar/proxy_with_sa_key.yaml @@ -47,7 +47,7 @@ spec: - name: cloud-sql-proxy # It is recommended to use the latest version of the Cloud SQL proxy # Make sure to update on a regular schedule! - image: gcr.io/cloud-sql-connectors/cloud-sql-proxy:2.0.0 # make sure to use the latest version + image: gcr.io/cloud-sql-connectors/cloud-sql-proxy:2.1.0 args: # If connecting from a VPC-native GKE cluster, you can use the # following flag to have the proxy connect over private IP diff --git a/examples/k8s-sidecar/proxy_with_workload_identity.yaml b/examples/k8s-sidecar/proxy_with_workload_identity.yaml index 2eeb3b3f3..af943c9cf 100644 --- a/examples/k8s-sidecar/proxy_with_workload_identity.yaml +++ b/examples/k8s-sidecar/proxy_with_workload_identity.yaml @@ -53,7 +53,7 @@ spec: - name: cloud-sql-proxy # It is recommended to use the latest version of the Cloud SQL proxy # Make sure to update on a regular schedule! - image: gcr.io/cloud-sql-connectors/cloud-sql-proxy:2.0.0 # make sure to use the latest version + image: gcr.io/cloud-sql-connectors/cloud-sql-proxy:2.1.0 args: # If connecting from a VPC-native GKE cluster, you can use the # following flag to have the proxy connect over private IP