Adding a subnet to an existing VPC

5 minutes 5 Questions

Adding a subnet to an existing VPC in Google Cloud is a fundamental networking task that allows you to expand your network topology and organize resources across different regions. A VPC (Virtual Private Cloud) is a global resource, while subnets are regional resources that define IP address ranges for your compute instances. To add a subnet to an existing VPC, you can use the Google Cloud Console, gcloud CLI, or Terraform. Using the Console, navigate to VPC Networks, select your existing VPC, click 'Add Subnet,' and specify the required parameters including subnet name, region, and IP address range. Using gcloud CLI, the command is: gcloud compute networks subnets create SUBNET_NAME --network=VPC_NAME --region=REGION --range=IP_RANGE Key considerations when adding subnets include: 1. IP Range Planning: Choose a CIDR range that does not overlap with existing subnets in the VPC or any peered networks. Common ranges include 10.0.0.0/8, 172.16.0.0/12, or 192.168.0.0/16. 2. Region Selection: Subnets are regional, so select the region where your resources will be deployed for optimal performance and compliance requirements. 3. Private Google Access: Enable this option if instances need to reach Google APIs and services using internal IP addresses. 4. Flow Logs: Consider enabling VPC Flow Logs for network monitoring and troubleshooting purposes. 5. Secondary Ranges: You can add secondary IP ranges for use with alias IP addresses, commonly used with GKE clusters. After creation, the subnet becomes available for VM instances, load balancers, and other resources in that region. Firewall rules at the VPC level apply to all subnets, but you can create specific rules targeting particular subnets using network tags or service accounts. Proper subnet design ensures efficient resource organization, security isolation, and scalability for your cloud infrastructure.

Adding a Subnet to an Existing VPC

Why It Is Important

Adding subnets to an existing Virtual Private Cloud (VPC) is a fundamental skill for cloud engineers. As organizations grow, their network requirements evolve. You may need to deploy resources in new regions, segregate workloads for security purposes, or accommodate new applications. Understanding how to expand your VPC network ensures you can scale infrastructure efficiently while maintaining proper network segmentation and security controls.

What It Is

A subnet is a range of IP addresses within your VPC. In Google Cloud Platform, VPCs use a global resource model, meaning a single VPC can span multiple regions. Subnets, however, are regional resources. When you add a subnet to an existing VPC, you are essentially allocating a new IP address range within a specific region where you can deploy compute resources like VM instances, GKE clusters, or Cloud SQL instances.

GCP supports two modes for subnet creation:
- Auto mode VPC: Automatically creates one subnet in each region with predefined IP ranges
- Custom mode VPC: Gives you full control over subnet creation, including IP ranges and regions

How It Works

To add a subnet to an existing VPC in GCP, you can use the Google Cloud Console, gcloud CLI, or Terraform. Here is the process:

Using gcloud CLI:

gcloud compute networks subnets create [SUBNET_NAME] --network=[VPC_NAME] --region=[REGION] --range=[IP_RANGE]

Key parameters include:
- --network: The name of the existing VPC
- --region: The region where the subnet will be created
- --range: The primary IP CIDR range for the subnet
- --secondary-range: Optional secondary ranges for alias IPs
- --enable-private-google-access: Allows VMs to reach Google APIs using internal IPs
- --enable-flow-logs: Enables VPC Flow Logs for the subnet

Important Considerations:
- Subnet IP ranges cannot overlap with other subnets in the same VPC
- You can expand subnet ranges but cannot shrink them
- Private Google Access and Flow Logs can be enabled during or after creation
- Secondary IP ranges are useful for GKE pod and service IPs

Exam Tips: Answering Questions on Adding a Subnet to an Existing VPC

1. Know the difference between auto mode and custom mode VPCs: Auto mode VPCs create subnets automatically, while custom mode requires manual subnet creation. You can convert auto mode to custom mode, but not the reverse.

2. Remember that subnets are regional: Unlike VPCs which are global, subnets exist within a single region. A subnet cannot span multiple regions.

3. Understand IP range requirements: Subnet IP ranges must be valid RFC 1918 private addresses and cannot overlap with existing subnets in the same VPC.

4. Know the gcloud command structure: Be familiar with the gcloud compute networks subnets create command and its key flags.

5. Recognize when to use secondary ranges: Questions about GKE or alias IP addresses often require knowledge of secondary subnet ranges.

6. Private Google Access is subnet-level: This setting is configured per subnet, not per VPC.

7. Subnet expansion: You can increase a subnet CIDR range, but you cannot decrease it. This is a common exam topic.

8. IAM permissions: Creating subnets requires the compute.subnetworks.create permission, typically granted through the Compute Network Admin role.

9. Look for keywords: When exam questions mention deploying resources in a new region within an existing VPC, the answer typically involves creating a new subnet in that region.
Test mode:
More Adding a subnet to an existing VPC questions
30 questions (total)

Other Ensuring Successful Operation of a Cloud Solution concepts

Active Assist for resource utilizationAdding custom static routes in a VPCAdding, editing, and removing node poolsAdjusting application traffic splittingAutoscaling node poolsBacking up and restoring database instancesCloud ProfilerCloud TraceConfiguring and deploying Ops AgentConfiguring audit logsConfiguring autoscaling for Cloud RunConfiguring GKE to access Artifact RegistryConfiguring log bucketsCreating and viewing imagesCreating Cloud Monitoring alertsCreating Cloud Monitoring custom metricsDeploying new Cloud Run application versionsEstimating costs of data storage resourcesExecuting queries to retrieve dataExpanding a subnet for more IP addressesExporting logs to BigQueryExporting logs to external systemsGemini Cloud Assist for Cloud MonitoringGKE nodes, Pods, and ServicesGoogle Cloud Managed Service for PrometheusHorizontal Pod autoscalingIndex advisorIngesting custom metrics from applicationsKubernetes PodsKubernetes ServicesKubernetes StatefulSetsLog analyticsLog routersManaging GKE Autopilot Pod resource requestsManaging objects in Cloud Storage bucketsObject lifecycle management policiesPersonalized Service Health dashboardQuerying AlloyDBQuerying BigQueryQuerying BigtableQuerying Cloud SQLQuerying FirestoreQuerying SpannerQuery InsightsRemotely connecting to Compute Engine instancesReserving static external IP addressesReserving static internal IP addressesReviewing job status (Dataflow, BigQuery)Scheduling snapshotsSecuring objects in Cloud Storage bucketsUsing Database CenterVertical Pod autoscalingViewing and filtering logs in Cloud LoggingViewing GKE cluster inventoryViewing log message detailsViewing running Compute Engine instancesWorking with Cloud DNSWorking with Cloud NATWorking with GKE node poolsWorking with Kubernetes resourcesWorking with snapshots and images