Cloud Run - VPC Serverless Connector and Direct VPC Egress cannot coexist?

[dheerajpanyam]

I have a Cloud Run Service that works fine for Direct VPC Egress with Cloud SQL. I now have a requirement to deploy managed REDIS and found that it cannot use the existing Direct VPC  egress setup possibly because it is not supported by managed REDIS only vpc serverless connector is supported. However this lead to a different issue that vpc serverless connector and direct vpc egress cannot coexist with a CR service.  So below questions

1. Is there a list of GCP services that support the newer Direct VPC egress and also a list of services that support vpc serverless connector?

The only solution in my case is to use vpc serverless connector for both Cloud SQL and managed REDIS.

[christianpaula · Accepted solution]

Hi @dheerajpanyam,

Welcome back to Google Cloud Community!

You're correct that Cloud Run Direct VPC Egress and VPC Serverless Connectors cannot coexist for the same service. This is because they both operate on different configurations and network interfaces within the Cloud Run environment.

Since Managed Redis doesn't support Direct VPC Egress, you'll need to use the VPC Serverless Connector for both Cloud SQL and Managed Redis. This will ensure compatibility and allow your Cloud Run service to access both services within the VPC network.

Documentation that might help:

• Compare Direct VPC egress and VPC connectors: https://cloud.google.com/run/docs/configuring/connecting-vpc
• Direct VPC egress with a VPC network: https://cloud.google.com/run/docs/configuring/connecting-vpc
• VPC Serverless Connector documentation: https://cloud.google.com/run/docs/configuring/vpc-connectors

Note: Direct VPC Egress is still in preview and has some limitations compared to VPC Serverless Connectors. Consider reviewing the features and limitations before making your decision.