Google Cloud's Shared VPC feature allows a host project to share its VPC network with one or more service projects, enabling Compute Engine instances in different projects to communicate using internal IPs as if they were on the same network, while each project retains its own resources. Shared VPC is an organization-level feature, so both projects must belong to the same Google Cloud organization before Shared VPC can be configured. The correct approach is to designate one project's VPC as the shared (host) network and attach the other project as a service project, rather than creating new VPCs, which would require re-architecting the network and does not match the requirement to enable traffic between the existing separate VPC groups.
Community Discussion