Virtual Private Clouds provide network isolation and custom addressing for CKS clusters
CoreWeave Virtual Private Clouds () define the network isolation configuration for attached CoreWeave products, like CKS clusters. VPCs let clusters securely communicate with resources in a , and with the public internet if desired, while preserving the privacy and security of the cluster’s network.This page introduces how CoreWeave VPCs work, the default VPC behavior for new CKS clusters, the prefix types you can configure, and when to define a custom VPC.
When you create your first CKS cluster through the Cloud Console, CoreWeave creates a default VPC in the same Zone as that cluster, unless you define a custom VPC. This default ensures that clusters have working network isolation without requiring upfront VPC configuration.
You can add custom VPC Prefixes to custom or default VPCs to allow communication with other VPCs in the same Region, with remote cloud providers, or with on-premises networks through a VPN or Direct Connect. Configure custom prefixes when your workloads need to reach networks outside the VPC. Add custom prefixes to a VPC through the Cloud Console during VPC creation, or during cluster creation at the network configuration step.You can configure two types of prefixes for VPCs:
Prefix type
Description
Host Prefixes
A range of IP addresses to assign to the Nodes within a VPC. Nodes use these addresses for network communications with other resources within the VPC.
VPC Prefixes
A range of IP addresses you can use to communicate with other VPCs in the same Region, with remote cloud providers, or with on-premises networks through a VPN or Direct Connect.
Each CoreWeave has a default Host Prefix, which CoreWeave assigns automatically unless you specify a different prefix.The default Host Prefixes for each AZ are:
You can’t modify or remove Host Prefixes after you add them to a VPC. CoreWeave assigns Host Prefixes when the Node boots, so you can’t modify them while the Node is running.
CoreWeave automatically creates a default VPC when you first create a cluster. The name of a new default VPC uses the following format:cw-vpc-[CLUSTER-NAME]-[SIX-DIGIT-STRING]To see the name of the default VPC, click the Customize option beside the default VPC selector during cluster creation.
When the default VPC doesn’t meet your network requirements, for example when you need custom addressing or connectivity to external networks, define a custom VPC instead. If you need a custom VPC configuration, define it by creating a VPC from the Cloud Console, or during the cluster creation process by defining a custom VPC.For more information, see VPC API reference.
