> ## 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. # How do I enable cross-cluster communication? The right approach depends on where the clusters live. ## 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](/platform/regions/about-regions-and-azs#single-az-cks-clusters) for the AZ constraint, and [VPC CIDR planning](/products/networking/vpc/vpc-cidr) 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 Egress` range on the receiving side. The NAT egress ranges for each AZ are listed on the [region pages](/platform/regions/about-regions-and-azs). * **[Tailscale Operator](/products/cks/clusters/coreweave-charts/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](/products/networking/direct-connect/about-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](/products/networking/vpc/about-vpcs). *** [Administrator](/support/networking/tags/administrator)