Plan Kubernetes pod CIDR, service CIDR, and node ranges for EKS, AKS, and GKE. Avoid overlap conflicts before cluster creation with instant validation and kubeadm output.
| Range | CIDR | Total IPs | Status |
|---|---|---|---|
| VPC / VNet | 10.0.0.0/16 | 65,536 | Valid |
| Service CIDR | 172.20.0.0/16 | 65,536 | Valid |
The Kubernetes CIDR Planner helps engineers design IP address ranges for Kubernetes clusters before provisioning. A cluster requires three non-overlapping CIDR blocks: the VPC or node CIDR (the real network), the pod CIDR (virtual addresses assigned to pods), and the service CIDR (virtual addresses assigned to ClusterIP services). Conflicts between these ranges cause routing failures that are difficult to fix after the cluster is running.
Select your provider (EKS, AKS, GKE, or generic kubeadm), enter your VPC CIDR, and adjust the pod CIDR, service CIDR, node mask size, and expected node and pod counts. The planner validates all three ranges for overlap and calculates how many nodes and pods the chosen CIDRs can support. Switch to the kubeadm or Terraform tabs to get the exact flags and resource blocks for your provider.
EKS uses the VPC CNI plugin, which assigns pod IPs directly from VPC subnets rather than a separate pod CIDR. AKS defaults to Azure CNI or kubenet; the planner targets Azure CNI. GKE uses alias IP ranges on subnets. Provider defaults are pre-filled but can be adjusted to match your existing network design.