Skip to content

Commit

Permalink
chore: update automation of Proxy version (#2175)
Browse files Browse the repository at this point in the history
  • Loading branch information
jackwotherspoon authored Apr 9, 2024
1 parent 088f47a commit a693acd
Showing 1 changed file with 4 additions and 2 deletions.
6 changes: 4 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -418,9 +418,10 @@ The containers have the proxy as an `ENTRYPOINT` so, to use the proxy from a
container, all you need to do is specify options using the command, and expose
the proxy's internal port to the host. For example, you can use:
<!-- {x-release-please-start-version} -->
```shell
docker run --publish <host-port>:<proxy-port> \
gcr.io/cloud-sql-connectors/cloud-sql-proxy:2.8.2 \
gcr.io/cloud-sql-connectors/cloud-sql-proxy:2.10.1 \
--address "0.0.0.0" --port <proxy-port> <instance-connection-name>
```
Expand All @@ -447,11 +448,12 @@ For example, a full command using a JSON credentials file might look like
docker run \
--publish <host-port>:<proxy-port> \
--mount type=bind,source="$(pwd)"/sa.json,target=/config/sa.json \
gcr.io/cloud-sql-connectors/cloud-sql-proxy:2.8.2 \
gcr.io/cloud-sql-connectors/cloud-sql-proxy:2.10.1 \
--address 0.0.0.0 \
--port <proxy-port> \
--credentials-file /config/sa.json <instance-connection-name>
```
<!-- {x-release-please-end} -->
## Running as a Kubernetes Sidecar
Expand Down

0 comments on commit a693acd

Please sign in to comment.