Skip to main content

GCP Compute Route

A Google Cloud Compute Route represents a single entry in the routing table of a Virtual Private Cloud (VPC) network. Each route specifies a destination IP CIDR range and a next-hop target (such as an instance, internet gateway, VPN tunnel, or IP address) that Google Cloud should use when forwarding traffic that matches the destination. Routes can be system-generated (implied or dynamic) or user-defined to steer traffic through appliances, interconnects, or external networks.
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

gcp-compute-network​

Every route belongs to exactly one VPC network. Overmind links the route to its parent gcp-compute-network so you can understand which network’s routing table will be affected if the route is changed or removed.

ip​

Routes contain both a destination CIDR and, in some cases, a next-hop IP address. These IP addresses are surfaced as ip resources, enabling you to trace where particular address ranges are advertised or which hosts act as next hops.

gcp-compute-instance​

When the next hop of a route is an instance (Next Hop Instance or Next Hop Ilb), the route is linked to that gcp-compute-instance. This association helps you evaluate the impact of deleting or modifying an instance that is being used to forward traffic.

gcp-compute-vpn-tunnel​

If the route’s next hop is a Cloud VPN tunnel, the route will be linked to the relevant gcp-compute-vpn-tunnel. This allows you to see which static or dynamic routes rely on a particular tunnel and to assess connectivity risks before altering the VPN configuration.