Skip to content

Epic: Networking — VPC, subnets, and firewall for dev #10

Description

@Chopsticks13

Networking Epic

Our dev project (ops-dev-7x2) has no network. Without one, nothing can run — no VMs, no GKE, no Cloud SQL with private IP.

What we're building

ops-dev-7x2
└── ops-dev-vpc (VPC)
    └── ops-dev-subnet (10.0.0.0/24, europe-west2)
        ├── Private Google Access: enabled
        └── Firewall rules
            ├── deny all ingress (baseline)
            ├── allow internal traffic (10.0.0.0/24)
            ├── allow IAP SSH (from Google's IAP range)
            └── allow health checks (from Google's health check ranges)

Work items

  1. Create modules/net-vpc — pure Terraform module

    • VPC with custom subnets (not auto-created)
    • Private Google Access per subnet
    • Optional flow logs
    • Optional secondary ranges (for future GKE pods/services)
  2. Create modules/net-vpc-firewall — pure Terraform module

    • Default deny-all-ingress
    • Built-in rules for health checks and IAP SSH
    • Custom ingress/egress rules via simple maps
  3. Create units + wire into stack

    • units/net-vpc/terragrunt.hcl
    • units/net-vpc-firewall/terragrunt.hcl
    • Add to live/terragrunt.stack.hcl under dev
    • VPC depends on project, firewall depends on VPC

How Fabric does it

GCP docs

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions