Virtual Private Clouds
Learn about Virtual Private Clouds on CoreWeave Kubernetes Service
CoreWeave Virtual Private Clouds (VPCs) define the network isolation configuration for attached CoreWeave products, like CKS clusters, allowing them to securely communicate with resources in a Region, and the public internet if desired, while maintaining privacy and security.
Default VPC
Each customer has a default VPC in each Region. The default VPC is automatically assigned to all clusters for that customer in that region, unless a custom VPC is specified in the cluster's manifest.
Multiple custom prefixes can be added to the default VPC to allow communication with other VPCs in the same region, or to remote Cloud providers or on-premises networks through a VPN or Direct Connect.
To create a custom prefix for the default VPC, use kubectl.
VPC HostPrefixes cannot be modified or removed after they are added to a VPC. HostPrefixes are assigned when the Node boots and cannot be modified while running.
Default VPC naming convention
The default VPC name for each customer's cluster is:
default-<REGION_NAME>
Where <REGION_NAME> is the region's name, a maximum of 10 characters.
For example, the default VPC name for a cluster in the RNO2 region is:
default-rno2
Custom VPC
If a custom VPC configuration is needed, define it by creating a VPC.
For more information, see VPC API reference.