Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(csql): update all v1 Cloud SQL Proxy usages to v2 #13194

Draft
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

jackwotherspoon
Copy link
Contributor

@jackwotherspoon jackwotherspoon commented Feb 27, 2025

Description

The Cloud SQL Proxy v2 was released in 2022, moving test infra and usage of v1 Proxy over to v2 syntax. v1 is heading towards deprecation.

Migration guide can be referenced for guidance.

Fixes #13123

@jackwotherspoon jackwotherspoon self-assigned this Feb 27, 2025
@product-auto-label product-auto-label bot added samples Issues that are directly related to samples. api: appengine Issues related to the App Engine Admin API API. api: cloudsql api: container Issues related to the Kubernetes Engine API API. api: run Issues related to the Cloud Run API. labels Feb 27, 2025
@jackwotherspoon
Copy link
Contributor Author

/gcbrun

@jackwotherspoon jackwotherspoon changed the title feat: update all v1 Cloud SQL Proxy usages to v2 feat(csql): update all v1 Cloud SQL Proxy usages to v2 Feb 28, 2025
@jackwotherspoon
Copy link
Contributor Author

I can see that v2 Cloud SQL Proxy is starting fine...

Cloud SQL proxy started for MySQL.
Cloud SQL proxy started for Postgres.
Cloud SQL proxy started for SQL Server.

@jackwotherspoon jackwotherspoon marked this pull request as ready for review February 28, 2025 18:36
@jackwotherspoon jackwotherspoon requested review from a team as code owners February 28, 2025 18:36
@jackwotherspoon jackwotherspoon marked this pull request as draft February 28, 2025 18:48
@jackwotherspoon
Copy link
Contributor Author

Moved back to draft, to fix tests.

@jackwotherspoon
Copy link
Contributor Author

Cloud SQL tests are all passing now...

cloud-sql/mysql/client-side-encryption................................[ SUCCESS]
cloud-sql/mysql/sqlalchemy............................................[ SUCCESS]
cloud-sql/postgres/client-side-encryption.............................[ SUCCESS]
cloud-sql/postgres/sqlalchemy.........................................[ SUCCESS]
cloud-sql/sql-server/client-side-encryption...........................[ SUCCESS]
cloud-sql/sql-server/sqlalchemy.......................................[ SUCCESS]

mountPath: /cloudsql
ports:
- containerPort: 8080
initContainers:
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

using newer native Kubernetes sidecar pattern: https://kubernetes.io/blog/2023/08/25/native-sidecar-containers/

@jackwotherspoon
Copy link
Contributor Author

jackwotherspoon commented Mar 3, 2025

The only official docs page that is affected by this change is https://cloud.google.com/python/django/kubernetes-engine which already telling users to install the v2 Cloud SQL Proxy (partially).

Will need to update one reference of docker pull gcr.io/cloudsql-docker/gce-proxy (v1 Proxy container) to use docker pull gcr.io/cloud-sql-connectors/cloud-sql-proxy which is v2 container.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api: appengine Issues related to the App Engine Admin API API. api: cloudsql api: container Issues related to the Kubernetes Engine API API. api: run Issues related to the Cloud Run API. samples Issues that are directly related to samples.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Upgrade Cloud SQL Proxy to v2 for tests
1 participant