CoreWeave use 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 if you need to know IP ranges in advance of integrating with existing environments, such as with Direct Connect. When planning your network architecture, ensure that you allocate sufficient IP addresses to accommodate your Nodes and their associated services. To convert CIDRs to IP address ranges, we recommend using the ARIN CIDR Calculator.Documentation Index
Fetch the complete documentation index at: https://docs.coreweave.com/llms.txt
Use this file to discover all available pages before exploring further.
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:Example vpc.yaml
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. |
If you have a smaller environment, you 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.
Planning CIDRs for connected VPCs
When connecting two CoreWeave Virtual Private Clouds (VPCs) between CKS clusters, make sure to plan unique, non-overlapping address space across the clusters. At a minimum, the two clusters must have non-overlapping internal Load Balancer CIDR blocks. To simplify routing between VPCs, the best practice is to ensure that all CIDR ranges used by each cluster, such as the Pod, Service, and Load Balancer CIDR, are non-overlapping. Set non-overlapping CIDR ranges when you create or edit each VPC in the Cloud Console. For the configuration flow, see Create and Manage VPCs. For automation, you can provision VPCs and their prefixes using the VPC API (for example, using thehostPrefixes and vpcPrefixes fields).
If you use Liqo for multi-cluster networking, its network fabric prefers NAT-less communication when PodCIDRs are disjoint, and applies address translation only when overlaps exist.