Skip to main content

GCP Compute Route

A Google Cloud Compute Route defines how packets are forwarded within a Virtual Private Cloud (VPC) network. Each route specifies a destination CIDR range and a next hop (such as an internet gateway, VPN tunnel, instance or peering connection), allowing Google Cloud to decide where to send traffic that matches the destination. Routes can be system-generated (for subnets and default internet egress) or user-defined to steer traffic through gateways, appliances or hybrid-connectivity links.
For full details see the official documentation: https://cloud.google.com/vpc/docs/routes

Terrafrom Mappings:

  • google_compute_route.name

Supported Methods​

  • GET: Get a gcp-compute-route by its "name"
  • LIST: List all gcp-compute-route
  • SEARCH

Possible Links​

gcp-compute-network​

Every route is created inside a single VPC network. Linking a route to its parent gcp-compute-network lets Overmind show which network’s traffic will be affected by that routing rule.

ip​

Routes specify a destination CIDR block and often a next-hop IP address. Associating the route with the relevant ip objects allows Overmind to surface the exact address ranges influenced by the route.

gcp-compute-instance​

When next_hop_instance is used, the route directs matching traffic to a specific Compute Engine VM. Linking to gcp-compute-instance reveals which workloads may become transit gateways or egress points because of the route.