DigitalOcean VPC

Deploys a Virtual Private Cloud (VPC) on DigitalOcean, providing a private, isolated network for Droplets, Kubernetes clusters, managed databases, and other resources within a single region. The component supports both explicit CIDR allocation and DigitalOcean's automatic IP range generation.

What Gets Created

When you deploy a DigitalOceanVpc resource, OpenMCF provisions:

• VPC — a digitalocean_vpc resource in the specified region, with an optional user-defined CIDR block or an auto-generated /20 range when no IP range is specified

Prerequisites

• DigitalOcean credentials configured via environment variables or OpenMCF provider config
• A target region selected from DigitalOcean's available datacenter regions
• CIDR planning (optional) — if you need a specific IP range, ensure it does not overlap with existing VPCs or DigitalOcean's reserved ranges (10.244.0.0/16, 10.245.0.0/16, 10.246.0.0/24, 10.229.0.0/16)

Quick Start

Create a file vpc.yaml:

apiVersion: digital-ocean.openmcf.org/v1
kind: DigitalOceanVpc
metadata:
  name: my-vpc
  labels:
    openmcf.org/provisioner: pulumi
    pulumi.openmcf.org/organization: my-org
    pulumi.openmcf.org/project: my-project
    pulumi.openmcf.org/stack.name: dev.DigitalOceanVpc.my-vpc
spec:
  region: nyc3

Deploy:

openmcf apply -f vpc.yaml

This creates a VPC in the NYC3 region with a DigitalOcean auto-generated /20 CIDR block (4,096 IPs).

Configuration Reference

Required Fields

Optional Fields

Examples

Dev VPC with Auto-Generated IP Range

A minimal VPC for development, letting DigitalOcean auto-assign a /20 CIDR block:

apiVersion: digital-ocean.openmcf.org/v1
kind: DigitalOceanVpc
metadata:
  name: dev-vpc
  labels:
    openmcf.org/provisioner: pulumi
    pulumi.openmcf.org/organization: my-org
    pulumi.openmcf.org/project: my-project
    pulumi.openmcf.org/stack.name: dev.DigitalOceanVpc.dev-vpc
spec:
  region: sfo3
  description: "Development environment VPC"

Staging VPC with Explicit /20 CIDR

A staging VPC with a specific IP range to avoid conflicts when peering with other VPCs:

apiVersion: digital-ocean.openmcf.org/v1
kind: DigitalOceanVpc
metadata:
  name: staging-vpc
  labels:
    openmcf.org/provisioner: pulumi
    pulumi.openmcf.org/organization: my-org
    pulumi.openmcf.org/project: my-project
    pulumi.openmcf.org/stack.name: staging.DigitalOceanVpc.staging-vpc
spec:
  region: fra1
  description: "Staging environment VPC"
  ipRangeCidr: "10.100.16.0/20"

Production VPC with Large /16 CIDR

A production VPC with the maximum /16 block (65,536 IPs) for workloads expected to scale, such as VPC-native Kubernetes clusters and managed databases:

apiVersion: digital-ocean.openmcf.org/v1
kind: DigitalOceanVpc
metadata:
  name: prod-vpc
  labels:
    openmcf.org/provisioner: pulumi
    pulumi.openmcf.org/organization: my-org
    pulumi.openmcf.org/project: my-project
    pulumi.openmcf.org/stack.name: prod.DigitalOceanVpc.prod-vpc
spec:
  region: nyc3
  description: "Production VPC for all services"
  ipRangeCidr: "10.101.0.0/16"
  isDefaultForRegion: true

Stack Outputs

After deployment, the following outputs are available in status.outputs:

Related Components

• DigitalOceanKubernetesCluster — deploys a managed Kubernetes cluster into the VPC
• DigitalOceanDatabaseCluster — provisions managed databases with private VPC connectivity
• DigitalOceanDroplet — creates Droplets placed within the VPC
• DigitalOceanLoadBalancer — provisions load balancers that route traffic to VPC resources
• DigitalOceanFirewall — controls network access to resources within the VPC