Managing Network Resources
Managing Compute Engine Resources
The course is part of this learning path
This course has been designed to teach you how to manage networking and compute resources on Google Cloud Platform. The content in this course will help prepare you for the Associate Cloud Engineer exam.
The topics covered within this course include:
- Adding subnets to a VPC
- Expanding existing subnets
- Reserving static addresses via the console and Cloud Shell
- Managing, configuring, and connecting to VM instances
- Adding GPUs and installing CUDA libraries
- Creating and deploying from snapshots and images
- Working with instance groups
- Learn how to manage networking and compute resources on Google Cloud Platform
- Prepare for the Google Associate Cloud Engineer Exam
- Those who are preparing for the Associate Cloud Engineer exam
- Those looking to learn more about managing GCP networking and compute features
To get the most from this course, you should have some exposure to GCP resources, such as VCPs, VM Instances, Cloud Console, and Cloud Shell. However, this is not essential.
Hi, everyone, and welcome to this lecture. In this lecture, we're going to talk a little bit about reserving static internal IP addresses. If you deploy a VM instance that requires a fixed internal IP address, you can obtain a static internal IP address for it in one of two ways. You can either simply reserve a new static internal address and then assign it to the new VM instance, or you can promote an existing ephemeral internal IP address to become a static internal IP address.
With static internal IPs, you can reserve internal IP addresses from the private RFC 1918 IP range that's configured within the subnet. You can then assign those reserved internal addresses to your resources as needed. Obviously, when you reserve an internal IP address, that IP address is taken out of the dynamic allocation pool. This prevents the address from being used for automatic allocations.
By leveraging reserved static internal IP addresses, you can ensure that the resource that is assigned the reserved address always uses the same IP address, even if the resource is deleted and recreated.
It's important to note before we dive into the demonstration that's up next, that the reservation of a static internal IP address requires specific IAM permissions. This ensures that only authorized users can reserve static internal IP addresses. I should also note that you can only reserve up to 200 static internal IP addresses per region, by default. Another thing to keep in mind is that the reservation of static internal IP addresses is only supported for VPC networks. You can't reserve static internal IP addresses for legacy mode networks.
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.