Google Cloud on Jhooq

Google Cloud Private Service Connect (PSC) Explained - Publish a Service with a Service Attachment and Consume It Through a PSC Endpoint

Fri, 09 Oct 2026 10:40:00 +0000

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 publish a single service, and any other team consume it over a private IP inside their own VPC, with the two networks never being joined at all.

Google Cloud Shared VPC Explained - Host Project, Service Project, networkUser and Cloud NAT (gcloud and Terraform)

Fri, 09 Oct 2026 10:30:00 +0000

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 - Shared VPC.

With Shared VPC there is only one network. One project (the host) owns it, and other projects (the service projects) simply borrow its subnets. The network team runs the network, the app teams run workloads on it, and nobody peers anything. We will build it end to end - host, service project, IAM, firewall, a VM in the service project sitting on the host's subnet - and then one Cloud NAT so that every workload in every service project goes out through a single egress IP.

Google Cloud Organization Setup with Cloud Identity Free - Create an Org and Move Your Projects Under It

Fri, 09 Oct 2026 10:20:00 +0000

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 who started with a personal Gmail account and a couple of projects do not have one.

Google Cloud Cross-Project VPC Peering - Peer Two VPCs in Different Projects (gcloud and Terraform)

Fri, 09 Oct 2026 10:10:00 +0000

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 networks which live in different projects.

The good news - it is the same peering primitive. The three things which change are the --peer-project flag, the fact that each side is created in its own project with its own permissions, and the Terraform, where we need two providers. And at the end we will hit the transitive trap again, which bites much harder across projects.

Google Cloud VPC Peering - Hub and Spoke Setup Step by Step with gcloud and Terraform

Fri, 09 Oct 2026 10:00:00 +0000

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 spoke VM over an internal IP, privately over Google's backbone.