Unbounded connection churn issue in gRPC-go

For the last 3 months I've been trying to get support from Google/gRPC/GCS teams to fix an issue with gRPC which results in thousands of connections and constant connection churn. The underlying issue appears to be a constant backend priority rotation with the endpoints for the client to connect to. The gRPC team seems unwilling to address why the gRPC client is opening several hundred connections when I'm not even using the client.

I was told to open a GCP support ticket and after many messages back and forth the ticket was closed because the discussion would continue on GitHub only for the issue to be closed a few weeks later.

I'm not the only one experiencing this issue either as a related issue was just posted in the google-cloud-go repo: https://github.com/googleapis/google-cloud-go/issues/14538.