CIDR Blocks in VPCs
Learn how VPCs use CIDR notation to define address ranges
CoreWeave VPCs use CIDR notation to define IP address ranges for the hosts, Pods, Load Balancers, and other Services used in each VPC.
Understanding CIDR blocks is especially useful for customers who need to know IP ranges in advance of integrating with existing environments, such as with Direct Connect.
Configuring CIDR blocks in VPCs
Below is an example YAML configuration for a single VPC containing multiple clusters, indicating the assignment of different CIDR ranges for different resources:
organizations:abc123:vpcs:default-us-east-04:hostPrefixes:- 10.176.192.0/18pubImport: truesite: us-east-04clusters:poc-gpu:version: v1.30site: us-east-04vpc: default-us-east-04podCIDR: 10.24.0.0/13serviceCIDR: 10.32.0.0/22internalLbCIDR: 10.32.4.0/22poc-cpu:version: v1.30site: us-east-04vpc: default-us-east-04podCIDR: 10.48.0.0/13serviceCIDR: 10.56.0.0/22internalLbCIDR: 10.56.4.0/22
CIDR block size guidelines
CIDR blocks for Nodes, Pods, Services, and Load Balancers have different subnet allocation limits. The following guidelines are based on the maximum number of resources that can be accommodated in each CIDR block:
Key | Value | Description |
---|---|---|
hostPrefixes | /18 | An /18 CIDR block accommodates clusters with up to 4,000 Nodes. Each Node requires 2 IP addresses. |
podCIDR | /13 | A /13 CIDR block allows up to 100 Pods per Node. |
serviceCIDR | /22 | A /22 CIDR block allows up to 1000 Services. |
internalLbCIDR | /22 | A /22 CIDR block allows up to 1000 Load Balancers. |
Customers with smaller environments may be able to use smaller CIDR ranges. For example, if the cluster is planned to have only 500 Nodes, a large CIDR block isn't required - however, using smaller CIDR ranges may limit future expansion, as Service IPs must be contiguous.