How to Map Custom Internal Domains to Cloud Run in a Shared VPC using Load Balancer

Are you trying to access your private Google Cloud Run services using a custom internal domain name (like internal.devopshq.in), but hit a wall with Cloud Run's native domain mapping limitations?

This is a common challenge in enterprise environments, especially when using Shared VPCs across different projects.

In this video, I walk through the complete, real-world solution to expose a Cloud Run service internally using a custom URL. We will bypass the limitations of native domain mapping by architecting a solution using an Internal Application Load Balancer (IALB) and Cloud DNS.

This is an advanced networking guide covering a multi-project Shared VPC setup.

We will cover:
✅ The limitations of Cloud Run Domain Mapping.
✅ The target architecture: Shared VPC (Host Project) vs. Service Project.
✅ Step 1: Preparing the Host Network (Proxy-Only Subnets & Firewalls).
✅ Step 2: Configuring Cloud Run for Internal Ingress.
✅ Step 3: The crucial IAM permissions needed for Shared VPC to work.
✅ Step 4: Deploying the Serverless NEG and Internal Load Balancer.
✅ Step 5: Mapping the private URL using Cloud DNS.
✅ Verification steps using a VM inside the VPC.

By the end of this video, you will have a secure, private, URL-accessible serverless application running on Google Cloud.

📄 Read the step-by-step written guide on:

---
Timestamps:
0:00 Introduction & The Problem
1:30 Architecture Overview (Shared VPC)
3:35 Shared VPC Setup (Subnets & Firewall)
5:15 Cloud Run Application Overview
5:30 Cloud Run Deployment
11:11 The Critical Step: Shared VPC IAM Permissions
16:32 Deploying the Internal Load Balancer
18:05 Creating the Serverless NEG & Reserve IP
21:03 Configuring Cloud DNS (A-Record)
22:42 Testing and Verification
23:00 Conclusion

Mapping custom domains: https://docs.cloud.google.com/run/doc...
Github Repo: https://github.com/i-adarsh/cloud/tre...


#GoogleCloud #CloudRun #SharedVPC #LoadBalancing #DevOps #GCPNetworking