This is the last post of my Google Cloud networking series, and it is about the tool I find the most elegant of them all - Private Service Connect, or PSC. With VPC peering we connected two whole networks. With Shared VPC we put many projects on one network. PSC does something much more surgical - it lets one team …

In the last two posts we connected networks with VPC peering and cross-project VPC peering, and both times we ran into the same wall - peering is not transitive, and every team still has to build and maintain its own VPC. In this blog post we are going to look at the way enterprises actually solve this on Google Cloud …

When I started the Shared VPC lab I hit a wall on the very first command - gcloud compute shared-vpc enable simply does not work on a standalone project. Shared VPC, Organization Policies, folders, hierarchical firewall policies and org-level IAM all need one thing first - a Google Cloud Organization. And most of us …

In the previous post on Google Cloud VPC peering we built a hub-and-spoke inside a single project. But in a real company that is almost never how it looks. The network team owns a hub in one project, and every application team has its own project with its own VPC. So in this blog post we are going to peer two VPC …

In this blog post we are going to look at Google Cloud VPC Network Peering - what it is, when you should use it instead of Shared VPC or a VPN, and then we are gonna build a complete hub-and-spoke lab step by step. Two VPC networks, two VMs with no public IP at all, and by the end of the post the hub VM pings the …