Your Google Cloud Architecture Diagrams Explained — Excerpt
Whether you use Google Cloud as your primary cloud or as a multi-cloud strategy, documenting your Google Cloud architecture is an important task. There are 2 options to build your GCP diagrams, either by hand (which you shouldn’t) or using an automated Google Cloud diagram software like Cloudockit, this article will be able to help you sort things out.
Let’s walk through each part of a global GCP architecture diagram together. The diagram example in this article has 5 main sections, a few sub-sections. Depending on the size of your Google Cloud infrastructure, you could have more or fewer sections.
The following diagram was created with Cloudockit and edited in diagrams.net.
1 — Virtual Private Cloud (VPC)
Virtual Private Cloud (VPC) provides networking functionality to a wide range of Google Cloud resources including Compute Engine virtual machine (VM) instances, Google Kubernetes Engine (GKE) clusters, and the App Engine flexible environment. VPC provides global, scalable, and flexible resources and services. Furthermore, VPC networks are logically isolated from each other in Google Cloud.
Subnet
Subnets are useful IP range partitions attributed to a specific region. Each VPC network consists of one or multiple subnets. When creating a subnet, a primary IP address range must be defined, and add secondary IP address ranges if desired.
Network interface card
A network interface is the point of interconnection between a computer and a private or public network.
Route tables
Google Cloud routes determine paths that network traffic takes from a VM instance to other destinations. These destinations can be inside your Google Cloud Virtual Private Cloud (VPC) network or outside of it.
In a VPC network, a route consists of a single destination prefix in CIDR format and a single next hop.
Continue reading at Cloudockit.
