Let me show you how to expand a subnet within GCP. I've gone ahead and created a custom subnet here with a slash 29 mask, and a slash 29 mask provides eight addresses, but four of those are reserved leaving me with another four for my VM instances. So I can click in here and you'll see that I already have four VM instances. So let's try to create another VM instance in this subnet. Now, the subnet is in US West1, so I'm going to go create an instance and specify the region for that. Without changing anything else I'm just going to try and click create. So as we can see I did not get a green check mark next to my instance, instead I get an exclamation sign, and if I have over that I get the actual error that the IP space of this specific subnet has been exhausted. So as expected, I can only create four VM instances with a slash 29 mask, but I want to show you how to expand that. So let's go ahead and go to the subnet and I'm going to directly click on my subnet and click the edit icon up here to now change this address range. So let's, for example, change that to a slash 24. That's going to allow over 200 instances in here and I'm just going to click save. Now I'm doing all of this without taking any of my VM instances down and we can see up here in the notification that this is currently being updated, and we can see here that it's now reflected. I now have this slash 24. So let's go back to my instance page and what I'm going to do is I'm actually just going to hit this retry button over here to see if I can recreate that instance within that subnet now that I've expanded it. So we can see that the instance has been created successfully and it's running, and that's how easy it is to expand a subnet in GCP without any workload shutdown or downtime.