Cloud Run to VPC, simplified

It just became easier, faster, and cheaper to call resources in your VPC from Cloud Run. Follow along as Xiaowen Xin, Product Manager, and Martin Omander, Developer Advocate, demonstrate how to get it done!
Chapters:
0:00 - Intro
1:18 - Cloud Run to VPC
2:00 - Example REST API
2:55 - How to set it up
4:32 - Connecting to on-prem systems
4:57 - Pricing
5:37 - Release status, limitations
6:09 - Cloud Run Jobs, Clud Functions
6:37 - Fine-grained access
7:14 - IP addresses
9:07 - Recap
Links:
Blog post → goo.gle/3PSx9MY
Docs → goo.gle/3FbZHvX
Example code → goo.gle/3RUAqOG
Checkout more episodes of Serverless Expeditions → goo.gle/ServerlessExpeditions​
Subscribe to Google Cloud Tech → goo.gle/GoogleCloudTech
#ServerlessExpeditions

[@googlecloudtech]

Subscribe to Google Cloud Tech → goo.gle/GoogleCloudTech

[@KevinBoutin]

So glad GCP came up with a successor to the serverless VPC connector. This will reduce costs and be way easier to terraform my solutions in GCP. I hope Apigee gets simplified as well. That is the most difficult deployment I have ever encountered on GCP.

[@avinashgadge4828]

wow....! Thanks!

[@btbutler55]

Hi. Very interesting new feature and I have a couple of questions. Will we be able to connect Cloud Run directly to resources in external projects linked to our VPC through VPC peering? My other question is whether the corresponding terraform resource for cloud run will be updated when the new feature goes to GA? Many thanks.

[@TheMomander]

Terraform modules are already available. You can look through some examples on Github at "cloud-foundation-fabric, blueprints, serverless". Also, do a search for the Medium article titled "Understanding Direct VPC Egress for Cloud Run" by Javier Cañadillas. It links to more samples.

[@jinaldesailive]

Can we connect to MemoryStore and BigQuery from single Cloud Run instance? Considering MemoryStore is in VPC and BigQuery obviously outside.

[@TheMomander]

Yes. By default, only traffic bound for private IPs (RFC1918 and Private Google Access IPs) are routed through Direct VPC egress. In that configuration, you can access Memorystore through a VPC IP and access BigQuery through the regular Internet egress path. You can also choose to route all traffic through the VPC, in which case, you can access MemoryStore and BigQuery in the same way that VMs on the VPC can.

[@meucanal5887]

Finally, my pocket thanks me for not needing the vpc connector anymore

[@tomcioss]

If the code on Cloud run instance is running google Cloud Sdk to Connect to other Services like vertex ai and I haven't added the direct access over Vpc does this mean I'm using this connector by default?

[@TheMomander]

Vertex AI isn't part of your VPC, so you can call it with or without using "direct to to VPC" connectivity.

[@Babbili]

Imagine doing that manually, creating network interfaces and bgp peering and figuring out why it's not working with nmap command and so 😂

[@guillaumeblaquiere]

Hey Martin, I'm Carrefour😂

[@TheMomander]

Hi Guillaume! I believe your name is visible at 1:50 🙂 Thank you for the great quote!

[@ng2250]

hey Carrefour, thanks a lot for your SO answers. chatgpt needs to weigh your responses more in training.

[@guillaumeblaquiere]

@@ng2250 🤣 ChatGPT will kill my points on SO!! 🤣

[@anhvancodon]

💗

[@sypen1]

Why does everything have to be so cringe

[@clowderclowder3964]

i love your honesty. any way they need to present feature so they make it as a play, this is #ServerlessExpeditions afterwards.