Deploying and Implementing Networking Resources
Deploying and Implementing Compute Engine Resources
This course has been designed to teach you how to deploy network and compute resources on Google Cloud Platform. The content in this course will help prepare you for the Associate Cloud Engineer exam.
- To understand key networking and compute resources on Google Cloud Platform
- Be able to explain different networking and compute features commonly used on GCP
- Be able to deploy key networking and compute resources on Google Cloud Platform
- Those who are preparing for the Associate Cloud Engineer exam
- Those looking to learn more about GCP networking and compute features
To get the most from this course then you should have some exposure to GCP resources, such as VPCs and Compute Instances. However, this is not essential.
About the Author
Tom is a 25+ year veteran of the IT industry, having worked in environments as large as 40k seats and as small as 50 seats. Throughout the course of a long an interesting career, he has built an in-depth skillset that spans numerous IT disciplines. Tom has designed and architected small, large, and global IT solutions.
In addition to the Cloud Platform and Infrastructure MCSE certification, Tom also carries several other Microsoft certifications. His ability to see things from a strategic perspective allows Tom to architect solutions that closely align with business needs.
In his spare time, Tom enjoys camping, fishing, and playing poker.
A VPC network is a virtual network that's deployed in the Virtual Private Cloud, hence the term VPC Network. Just like any other physical network, a VPC network provides connectivity for VMs, Kubernetes clusters, and many other resources that need to communicate.
In this lesson, we're going to talk a little bit about VPC networks, their properties, and the different types of VPC networks that are available to you. Once we've covered the basics of VPC networks, we'll work through a demo so you can see how a VPC network is deployed.
Now, before we get into the two types of VPC networks that are available, what I want to do is briefly touch on subnets and the role that they play. Any VPC network that's created will need to have at least one subnet defined before the network can be used. This is because VPC networks, themselves, do not have any IP address ranges associated with them. Instead, IP ranges are defined for the subnets which are defined within the network itself.
The type of VPC network that you deploy will determine how the initial subnet for the network is deployed. GCP offers two types of VPC networks, determined by their subnet creation mode.
Creating an auto mode network results in one subnet from each region to automatically be created within the network. The subnets that are automatically created use a set of predefined IP ranges from the 10.128.0.0/9 CIDR block.
Now, while an auto mode VPC network automatically creates subnets, this does not preclude you from adding additional subnets manually, as needed. However, any manually added subnets that you create need to use IP ranges outside of 10.128.0.0/9 range.
Alternatively, you can also create what's called a custom mode network. When a custom mode network is created, it's created with no subnets at all. In practice, you would typically deploy custom mode networks when you need more control over the subnets and IP ranges that are provisioned within them.
In the upcoming demonstration, I'm going to show you how to deploy a custom mode network. After deploying the network, I'll show you how to create a single subnet within the network.