Skip to content

Update dev VPC CIDR to 10.1.0.0/16 #8

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
averyjennings wants to merge 1 commit into
base: main
Choose a base branch
from
+1 −1
Open

Update dev VPC CIDR to 10.1.0.0/16 #8

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion dev/vpc/terragrunt.hcl
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ terraform {
}

inputs = {
vpc_cidr = "10.0.0.0/16"
vpc_cidr = "10.1.0.0/16"
Copy link

@coderabbitai coderabbitai bot Dec 15, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🏁 Script executed:

# First, check if the file exists and read its content
ls -la dev/vpc/terragrunt.hcl 2>/dev/null || echo "File not found"

Repository: coderabbitai/rabbits-playground

Length of output: 145

🏁 Script executed:

# Search for CIDR allocation references in the codebase
rg "10\.[0-3]\.0\.0/16" --type hcl --type tf --type json -A 2 -B 2

Repository: coderabbitai/rabbits-playground

Length of output: 102

🏁 Script executed:

# Look for network configuration or CIDR documentation
find . -type f \( -name "*network*" -o -name "*cidr*" -o -name "*allocation*" \) -iname "*.md" -o -iname "*.txt" -o -iname "*.yaml" | head -20

Repository: coderabbitai/rabbits-playground

Length of output: 57

🏁 Script executed:

# Search for references to Production and Development VPC CIDR in configuration files
rg -i "(production|development|prod|dev).*cidr|vpc.*10\." --type hcl --type tf --type yaml -B 2 -A 2

Repository: coderabbitai/rabbits-playground

Length of output: 102

🏁 Script executed:

# Look for VPC peering, route tables, and security group rules that might be affected
rg -i "(vpc_peering|route_table|security_group|transit.*gateway)" --type hcl --type tf | head -30

Repository: coderabbitai/rabbits-playground

Length of output: 102

🏁 Script executed:

# Read the actual file content
cat -n dev/vpc/terragrunt.hcl

Repository: coderabbitai/rabbits-playground

Length of output: 512

🏁 Script executed:

# Search for CIDR patterns across all files without file type filtering
rg "10\.[0-3]\.0\.0/16" -B 2 -A 2

Repository: coderabbitai/rabbits-playground

Length of output: 834

🏁 Script executed:

# Search for any references to production/development CIDR across the codebase
rg "(vpc_cidr|CIDR|cidr)" -i --type-list | head
rg "(vpc_cidr|CIDR|cidr)" -i -B 1 -A 1

Repository: coderabbitai/rabbits-playground

Length of output: 3740

🏁 Script executed:

# Look for documentation files that might contain CIDR allocations
find . -type f \( -name "*.md" -o -name "*.txt" -o -name "*.rst" \) | xargs grep -l -i "cidr\|network\|allocation" 2>/dev/null | head -10

Repository: coderabbitai/rabbits-playground

Length of output: 86

🔍 Additional research query:

Search Notion for network CIDR allocation table and network engineering requirements for VPC changes. Look for documentation about production and development CIDR ranges (10.0.0.0/16, 10.1.0.0/16, 10.2.0.0/16, 10.3.0.0/16).

💡 Result:

Network CIDR Allocation Documentation

I found the comprehensive Network CIDR Allocation Table in Notion with detailed information about your VPC network configuration:

VPC CIDR Assignments

The document defines IP address allocation for all VPCs in AWS infrastructure, coordinated with on-premises network teams to prevent routing conflicts.

CIDR Range Allocations:

  • Development: 10.0.0.0/16 (Active - Primary dev workloads)
  • Production: 10.1.0.0/16 (Active - Production services)
  • Staging: 10.2.0.0/16 (Reserved - Future staging environment)
  • DR: 10.3.0.0/16 (Reserved - Disaster recovery site)

Subnet Architecture Within VPCs

Each /16 VPC is subdivided with:

  • 10.x.0.0/20, 10.x.16.0/20, 10.x.32.0/20 - Public subnets (AZ-a, AZ-b, AZ-c)
  • 10.x.128.0/20, 10.x.144.0/20, 10.x.160.0/20 - Private subnets (AZ-a, AZ-b, AZ-c)

VPC Change Requirements & Network Engineering Approval Process

⚠️ Do not modify CIDR allocations without Network Engineering approval. Changing a VPC's CIDR range requires:

  1. VPC peering updates
  2. Route table modifications
  3. Security group rule updates
  4. Transit Gateway attachment changes
  5. DNS resolver rule updates

Network Integration Context

The corporate network uses 172.16.0.0/12, and the 10.x.0.0/8 ranges are specifically allocated for AWS to avoid overlap with corporate offices (172.16.0.0/16), data centers (172.17.0.0/16), and VPN clients (172.18.0.0/16).

Contact: [email protected] for CIDR allocation requests.,

CRITICAL: CIDR conflict with Production - DO NOT MERGE.

Both dev/vpc/terragrunt.hcl and prod/vpc/terragrunt.hcl are assigned 10.1.0.0/16. According to the Network CIDR Allocation Table, development should use 10.0.0.0/16 and production should use 10.1.0.0/16. This creates a direct routing conflict.

Update vpc_cidr to the correct development range 10.0.0.0/16 on line 14. CIDR changes require Network Engineering approval and updates to VPC peering, route tables, security groups, Transit Gateway attachments, and DNS resolver rules.

🤖 Prompt for AI Agents 
In dev/vpc/terragrunt.hcl around line 14, the vpc_cidr is incorrectly set to
10.1.0.0/16 which conflicts with prod; change it to the correct dev CIDR
10.0.0.0/16 on line 14, then submit the CIDR change to Network Engineering for
approval and coordinate updates to VPC peering, route tables, security groups,
Transit Gateway attachments, and DNS resolver rules as required.

cluster_name = "dev-eks-cluster"
single_nat_gateway = true # Cost optimization for dev
}