From 189cd4ef5c0c4139a592dbae4f188c49a4f58b22 Mon Sep 17 00:00:00 2001 From: Jack Wotherspoon Date: Fri, 14 Jun 2024 09:52:21 -0400 Subject: [PATCH] chore: bump proxy version in examples --- examples/k8s-health-check/README.md | 2 +- examples/k8s-health-check/proxy_with_http_health_check.yaml | 2 +- examples/k8s-service/README.md | 2 +- examples/k8s-service/pgbouncer_deployment.yaml | 2 +- examples/k8s-sidecar/README.md | 2 +- examples/k8s-sidecar/job_with_shutdown_hook.yaml | 2 +- examples/k8s-sidecar/proxy_with_sa_key.yaml | 2 +- examples/k8s-sidecar/proxy_with_workload_identity.yaml | 2 +- 8 files changed, 8 insertions(+), 8 deletions(-) diff --git a/examples/k8s-health-check/README.md b/examples/k8s-health-check/README.md index e4540f024..c06470985 100644 --- a/examples/k8s-health-check/README.md +++ b/examples/k8s-health-check/README.md @@ -173,7 +173,7 @@ for more than 1 minute. - name: my-application image: gcr.io/my-container/my-application:1.1 - name: cloud-sql-proxy - image: gcr.io/cloud-sql-connectors/cloud-sql-proxy:2.8.0 + image: gcr.io/cloud-sql-connectors/cloud-sql-proxy:2.11.4 args: # Set the --max-connections flag to 50 - "--max-connections" 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 6d4d0a561..adc5db29d 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 Auth Proxy # Make sure to update on a regular schedule! - image: gcr.io/cloud-sql-connectors/cloud-sql-proxy:2.8.0 + image: gcr.io/cloud-sql-connectors/cloud-sql-proxy:2.11.4 imagePullPolicy: IfNotPresent args: diff --git a/examples/k8s-service/README.md b/examples/k8s-service/README.md index eecb33d8d..76938eaaa 100644 --- a/examples/k8s-service/README.md +++ b/examples/k8s-service/README.md @@ -171,7 +171,7 @@ For the PgBouncer deployment, we add the proxy as a sidecar, starting it on port ``` yaml - name: cloud-sql-proxy - image: gcr.io/cloud-sql-connectors/cloud-sql-proxy:2.8.0 # make sure to use the latest version + image: gcr.io/cloud-sql-connectors/cloud-sql-proxy:2.11.4 # make sure to use the latest version args: # Replace DB_PORT with the port the proxy should listen on - "--port=" diff --git a/examples/k8s-service/pgbouncer_deployment.yaml b/examples/k8s-service/pgbouncer_deployment.yaml index ad7710245..516a2ba09 100644 --- a/examples/k8s-service/pgbouncer_deployment.yaml +++ b/examples/k8s-service/pgbouncer_deployment.yaml @@ -84,7 +84,7 @@ spec: - name: cloud-sql-proxy # It is recommended to use the latest version of the Cloud SQL Auth Proxy # Make sure to update on a regular schedule! - image: gcr.io/cloud-sql-connectors/cloud-sql-proxy:2.8.0 + image: gcr.io/cloud-sql-connectors/cloud-sql-proxy:2.11.4 args: - "--port=5431" - "" diff --git a/examples/k8s-sidecar/README.md b/examples/k8s-sidecar/README.md index 4536c328a..334d59e58 100644 --- a/examples/k8s-sidecar/README.md +++ b/examples/k8s-sidecar/README.md @@ -182,7 +182,7 @@ as a separate service for several reasons: - name: cloud-sql-proxy # It is recommended to use the latest version of the Cloud SQL Auth Proxy # Make sure to update on a regular schedule! - image: gcr.io/cloud-sql-connectors/cloud-sql-proxy:2.8.0 # make sure to use the latest version + image: gcr.io/cloud-sql-connectors/cloud-sql-proxy:2.11.4 # make sure to use the latest version 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/job_with_shutdown_hook.yaml b/examples/k8s-sidecar/job_with_shutdown_hook.yaml index 67b41a281..f0799a027 100644 --- a/examples/k8s-sidecar/job_with_shutdown_hook.yaml +++ b/examples/k8s-sidecar/job_with_shutdown_hook.yaml @@ -58,7 +58,7 @@ spec: - name: cloud-sql-proxy # It is recommended to use the latest version of the Cloud SQL Auth Proxy # Make sure to update on a regular schedule! - image: gcr.io/cloud-sql-connectors/cloud-sql-proxy:2.8.0 + image: gcr.io/cloud-sql-connectors/cloud-sql-proxy:2.11.4 args: # Enable the admin api server on port 9091 - "--admin-port=9091" diff --git a/examples/k8s-sidecar/proxy_with_sa_key.yaml b/examples/k8s-sidecar/proxy_with_sa_key.yaml index 45691ec44..20ba048c3 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 Auth Proxy # Make sure to update on a regular schedule! - image: gcr.io/cloud-sql-connectors/cloud-sql-proxy:2.8.0 + image: gcr.io/cloud-sql-connectors/cloud-sql-proxy:2.11.4 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 132ca58aa..80e25df23 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 Auth Proxy # Make sure to update on a regular schedule! - image: gcr.io/cloud-sql-connectors/cloud-sql-proxy:2.8.0 + image: gcr.io/cloud-sql-connectors/cloud-sql-proxy:2.11.4 args: # If connecting from a VPC-native GKE cluster, you can use the # following flag to have the proxy connect over private IP