Reference Architecture: NAT Gateway for DOKS and Droplet (#27)

[CODEBRAKERBOYY]

This PR adds a new reference architecture demonstrating NAT Gateway routing for both DOKS cluster workloads and Droplets.

-- Includes:

• VPC, NAT Gateway, and DOKS cluster with Routing Agent enabled
• Droplet configured to route egress via NAT Gateway
• Route CRD that overrides 0.0.0.0/0 to NAT Gateway gateway IP
• Terraform modules separated into infra and routes
• README with apply, verify, and cleanup instructions

-- Verified:

• terraform fmt and terraform validate passed successfully

[do-joe]

Hi @CODEBRAKERBOYY thanks for contribution.

This resource config doesn't match the digitalocean_vpc_nat_gateway resource schema. The schema looks like this:

resource "digitalocean_vpc_nat_gateway" "my-vpc-nat-gateway" {
  name   = "terraform-example"
  type   = "PUBLIC"
  region = "nyc3"
  size   = "1"
  vpcs {
    vpc_uuid = digitalocean_vpc.my-vpc.id
  }
  udp_timeout_seconds  = 30
  icmp_timeout_seconds = 30
  tcp_timeout_seconds  = 30
}

https://registry.terraform.io/providers/digitalocean/digitalocean/latest/docs/resources/vpc_nat_gateway

I'm curious if found the schema you used in other docs or where the one you used came from.

[CODEBRAKERBOYY]

Thanks for the feedback @do-joe
You’re right my configuration didn’t fully align with the current digitalocean_vpc_nat_gateway schema. I’ll update the resource block to match the official format and re-run terraform fmt and terraform validate.
I’ll push the corrected version shortly.