We run various services (e.g. pgadmin) that use cloud sql proxy as a sidecar to enable IAM-based auth. We have ~100 cloud sql instances, and each of our services (e.g. pgadmin) supports connecting to any of these. Some instances may be connected to rarely, others more frequently.
Whenever cloud sql proxy starts (or restarts), if any of the instances on the command-line have been deleted (or are misconfigured, or are denied by IAM), the proxy will exit with an error. This then causes the service (e.g. pgadmin) to not be able to connect to any of the instances until the issue is addressed. This is particularly problematic if the restart was automatic (many of these services run in GKE/Cloud Run).
Is it possible to better support this case and not let an issue with an instance prevent proxying all the others? We are willing to contribute a PR, if there is a simple solution that your team would accept. Or perhaps there is some feature I've missed that could solve this already.
Would it make sense to add a command-line flag to allow disregarding bad instances (i.e. just log and continue)?
Sample code Alternatives ConsideredWe have considered a few alternatives:
No response
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4