Clusters in the same Availability Zone
A VPC is scoped to a single Availability Zone, so clusters in the same AZ can share one VPC and communicate over that private network. See About Regions and Availability Zones for the AZ constraint, and VPC CIDR planning for an example of multiple clusters in one VPC.Clusters in different AZs, regions, or organizations
Because VPCs do not span AZs, cross-AZ cluster communication requires one of the following:- Public LoadBalancer Services with an allowlist. Expose the target Service to the public internet and allowlist the source cluster’s
NAT Egressrange on the receiving side. The NAT egress ranges for each AZ are listed on the region pages. - Tailscale Operator. Deploys a Tailscale mesh inside the cluster for secure access to in-cluster resources from other clusters or networks.
Connecting from outside CoreWeave
Direct Connect provides a dedicated private path between an on-premises or hyperscaler network and a CoreWeave VPC, bypassing the public internet. It is the right choice for hybrid setups, not for cluster-to-cluster traffic between CoreWeave clusters. For VPC fundamentals, see About VPCs.Administrator