Cloud

Choose CIDR Ranges

Choosing appropriate Classless Inter-Domain Routing (CIDR) ranges is essential for successful VPC peering between Redpanda and your cloud network.

These guidelines provide general recommendations for choosing non-conflicting CIDR ranges. If you have a complex networking setup, work with a networking engineer to identify Redpanda CIDRs that won’t conflict with your existing VPCs.

Prerequisites

  • VPC or virtual network (VNet): Before setting up a peering connection in Redpanda Cloud, you must have another VPC or VNet to which Redpanda can connect. If you do not already have a network, create one in your cloud provider.

  • Matching region: VPC peering connections can only be established between networks created in the same region. Redpanda Cloud does not support inter-region VPC peering connections.

Consider adding an rp- prefix to the VPC or VNet name to indicate that it is for deploying a Redpanda cluster.

Supported IP address ranges

Redpanda Cloud uses private IPv4 address spaces for cluster CIDRs. These ranges are designed for internal networks and cannot be accessed directly from the internet. Choose a CIDR from one of the following RFC 1918 ranges:

  • 10.0.0.0/8 - Provides addresses from 10.0.0.0 through 10.255.255.255

  • 172.16.0.0/12 - Provides addresses from 172.16.0.0 through 172.31.255.255

  • 192.168.0.0/16 - Provides addresses from 192.168.0.0 through 192.168.255.255

For BYOC and Dedicated clusters, client networks that connect to the cluster, including peered VPCs and VNets, can also use the RFC 6598 Carrier-Grade NAT (CGNAT) address space:

  • 100.64.0.0/10 - Provides addresses from 100.64.0.0 through 100.127.255.255

When Redpanda creates the network for your cluster, the CIDR you specify must come from an RFC 1918 range (10.0.0.0/8, 172.16.0.0/12, or 192.168.0.0/16).

Redpanda’s network infrastructure routes traffic only within these RFC 1918 and RFC 6598 address spaces. Redpanda does not route packets to other IP spaces. Traffic from public IP addresses or other private ranges outside these specifications is blocked by design.

What are CIDRs?

The following CIDR ranges are a critical part of your Redpanda cluster’s network configuration:

  • Your existing (client) VPC/VNet CIDR

  • Your Redpanda cluster CIDR

It is important to ensure that these ranges do not overlap when setting up VPC peering.

Choose the CIDR ranges

To choose a range for Redpanda, you must know your VPC/VNet CIDR:

  • In AWS, find it in the VPC area of the AWS Management Console, labeled IPv4 CIDRs.

  • In Azure, find it in the Essentials view of your virtual network, labeled Address space.

  • In GCP, find it in the Details view of your VPC, labeled Internal IP Ranges.

You can check which IPs this range encompasses by using either the ipcalc command in your terminal or the CIDR calculation tool. For example, if your client’s CIDR range is 10.0.0.0/20, run:

ipcalc 10.0.0.0/20

The output should look similar to the following:

Address:   10.0.0.0             00001010.00000000.0000 0000.00000000
Netmask:   255.255.240.0 = 20   11111111.11111111.1111 0000.00000000
Wildcard:  0.0.15.255           00000000.00000000.0000 1111.11111111
=>
Network:   10.0.0.0/20          00001010.00000000.0000 0000.00000000
HostMin:   10.0.0.1             00001010.00000000.0000 0000.00000001
HostMax:   10.0.15.254          00001010.00000000.0000 1111.11111110
Broadcast: 10.0.15.255          00001010.00000000.0000 1111.11111111
Hosts/Net: 4094                  Class A, Private Internet

Note the values for HostMin (10.0.0.1) and HostMax (10.0.15.254). These are the minimum and maximum values of the range of 4,094 IPs that this CIDR covers. The number of IPs is governed by the suffix: /16 contains 65534 IPs, /21 contains 2046, /24 contains 254, and so on. For private networks, this number can range from 8 (which contains 16777214 IPs) to 30 (which contains 2).

The Redpanda CIDR must be between /16 and /20. For the subnets Redpanda creates inside it, see Address space used by standard BYOC clusters.

Example

Assume that your client’s CIDR range is 10.0.0.0/20. Your Redpanda range cannot overlap with it; if it does, VPC peering will not work.

A limited set of examples that work with 10.0.0.0/20 are 10.8.0.0/20, 10.0.16.0/20, or 10.1.0.0/20.

Ranges like 10.0.0.0/16 or 10.0.0.0/19, which contain 10.0.0.0/20, would not work. You can use ipcalc to check for overlapping IPs.

Multi-VPC/VNet example

If you have many IP ranges allocated in a complex system, work with a network engineer who can help with IP allocation. Your Redpanda CIDR cannot overlap with any of your existing VPCs/VNets, nor can it overlap with the VPC/VNet you want to peer with.

Assume that the following example ranges are in use:

  • 10.0.0.0/20

  • 10.8.0.0/20

  • 10.0.32.0/20

  • 10.0.16.0/20

A Redpanda CIDR that would work (and not overlap) with any of them is 10.8.48.0/20.

Address space used by standard BYOC clusters

When Redpanda creates the network for a standard BYOC cluster, it creates the cluster’s subnets inside the CIDR block you choose for the network. On GCP and Azure, Redpanda puts the subnets of each cluster in a smaller block inside the network CIDR. This page calls it the cluster block. The cluster block is a /20. On GCP, it is a /19 when the network CIDR is /19 or larger (more addresses, such as /19 or /16). Reserve the whole network CIDR for Redpanda: Don’t assign its addresses to other networks or resources, and don’t connect the Redpanda network to a network that uses any part of it.

The network CIDR must be /20 or larger. A /20 holds every subnet in the default layouts below. On GCP, a /19 or larger network CIDR uses a larger layout.

Address counts include every address in each range, including the addresses that your cloud provider reserves in each subnet. On GCP and Azure, the Unallocated row is the rest of the block, which Redpanda reserves.

  • AWS

  • GCP

  • Azure

In a standard cluster, Redpanda creates /24 subnets at the start of your network CIDR: two private and two public subnets in each of three availability zones. Redpanda reserves space for three zones even for a single-zone cluster.

Subnet Count Size Addresses each Total addresses

Private subnets

6

/24

256

1,536

Public subnets

6

/24

256

1,536

Reserved, used by clusters that use Redpanda Agentic Data Plane

1

/22

1,024

1,024

Total

/20

4,096

If the network CIDR is /20, Redpanda creates these ranges within the cluster’s /20 block:

Range Count Size Addresses each Total addresses

Primary range for nodes

1

/24

256

256

Secondary range for Kubernetes services

1

/24

256

256

Secondary range for pods

1

/21

2,048

2,048

Google Kubernetes Engine (GKE) control plane

1

/28

16

16

Private Service Connect NAT subnets, reserved even if you don’t use Private Service Connect

2

/26

64

128

Unallocated

1,392

Total

/20

4,096

If the network CIDR is /19 or larger, new GCP clusters use a larger layout in a /19 cluster block instead:

Range Count Size Addresses each Total addresses

Primary range for nodes

1

/24

256

256

Secondary range for Kubernetes services

1

/22

1,024

1,024

Secondary range for pods

1

/20

4,096

4,096

GKE control plane

1

/28

16

16

Private Service Connect NAT subnets, reserved even if you don’t use Private Service Connect

2

/26

64

128

Unallocated

2,672

Total

/19

8,192

Redpanda sets the layout when it creates the cluster. Redpanda does not change the layout later. Choose a /19 or larger network CIDR if you expect many Redpanda Connect pipelines or plan to use Redpanda Agentic Data Plane.

Redpanda creates these subnets within the cluster’s /20 block:

Subnet Count Size Addresses each Total addresses

First range of the block, left unused

1

/24

256

256

Redpanda agent

2

/28

16

32

Node pools for the system, Redpanda Connect, Kafka Connect, and Redpanda SQL

4

/27

32

128

Redpanda broker nodes

3

/26

64

192

Pods and Kubernetes services

8

/24

256

2,048

Unallocated

1,440

Total

/20

4,096

Clusters created earlier can use a different layout, and Redpanda doesn’t resize or move a cluster’s existing subnets. For BYOVPC and BYOVNet clusters, you create the subnets yourself. See Create a BYOVPC Cluster on AWS, Create a BYOVPC Cluster on GCP, or Create a BYOVNet Cluster on Azure.