VPC Network
Does ZopNight manage VPC Network?
A GCP VPC network is free, since no meter attaches to the network object itself, yet it anchors everything that is not: egress, peering traffic, NAT, and the subnets and firewall rules inside it. ZopNight discovers VPCs via Cloud Asset Inventory as the root of network topology for all attached resources.
Rules that fire on VPC Network
No active rule family targets VPC Network today. Rules that used to are retired, and retired rules publish no pages and fire no findings. Scheduling and permissions coverage are unaffected.
A VPC network is the global software-defined network that contains subnets, routes, and firewall rules for a project. VPCs are free but anchor everything that is not, and orphaned VPCs signal abandoned environments.
A free object that anchors paid traffic
The VPC itself has no meter: creating one, keeping one, or keeping ten costs nothing directly. What costs money is what moves through it. Egress leaving Google’s network bills per GB, traffic crossing a VPC peering bills on both sides of the arrangement, Cloud NAT and VPN gateways attached to the network carry their own charges, and every reserved address, forwarding rule, and VM inside it meters under its own type. A VPC is therefore best read as a ledger heading (the container under which a project’s real network costs accumulate) rather than a cost item.
VPCs as topology roots in ZopNight
ZopDev discovers VPCs via Cloud Asset Inventory as the root of network topology for all attached resources. Everything else in the networking family on this directory, from subnets and firewall rules to routers, peerings, and addresses, hangs off a VPC, and the discovery model reflects that: the network is the join key that lets a flagged idle address or dead forwarding rule be traced to the environment it belonged to. There is nothing to schedule on a network, and being free, nothing to rightsize either.
What an orphaned network is telling you
An orphaned VPC is a strong signal of an abandoned environment: no running compute, stale firewall rules, and subnets nobody recognizes. Abandoned environments rarely clean up only their free parts. When ZopNight shows a VPC whose attached resources have dwindled to leftovers, the productive move is to sweep the whole container: reserved addresses still billing hourly, peerings still active toward networks that no longer need them, NAT gateways idling, and DNS records pointing into the empty network. The default network auto-created in new projects is a common member of this category.
Inspecting VPC networks in the console
Google Cloud console → VPC network → VPC networks lists each network with its subnet count and mode (auto or custom). Clicking through to a network’s subnets, firewall rules, and peering tabs gives the full picture of what the free container is holding, and what paid debris a teardown left inside it.