Oracle Cloud Infrastructure Documentation

Workload Cluster Network CIDR Ranges (VCN-Native Pod)

Learn about network CIDR ranges used with VCN-Native pods on Compute Cloud@Customer.

Throughout this documentation, variables are used to represent CIDR ranges for instances in different subnets. The following table lists the CIDR variables and example values for use with VCN-Native Pod Networking.

Note

These are examples only. The CIDR ranges you use depend on the number of clusters you have, the number of nodes in each cluster, the shape you select for the worker nodes, and the type of networking you're using.

For VCN-Native Pod Networking, every pod gets an IP address assigned from the IP address pool that's defined in the pod subnet CIDR. The shape you specify for the node pool determines the maximum number of VNICs (pods) for each worker node, as described in Node Shapes and Number of Pods.

The primary difference between IP address requirements of VCN-Native Pod Networking and Flannel Overlay networking is that VCN-Native Pod Networking requires more IP addresses to be available. The table in Workload Cluster Network CIDR Ranges (Flannel Overlay) shows smaller CIDR ranges than the following table for VCN-Native Pod Networking CIDR ranges.

Example CIDR Values to Use with VCN-Native Pod Networking

Variable Name

Description

Example Value

vcn_cidr

VCN CIDR range

This Is a small VCN with 8192 IP's for creating OKE infrastructure.

172.31.0.0/19

worker_cidr

Worker subnet CIDR

172.31.8.0/21

workerlb_cidr

Worker load balancer subnet CIDR

172.31.0.0/23

kmi_cidr

OKE control plane subnet CIDR

172.31.4.0/22

kmilb_cidr

OKE control plane load balancer subnet CIDR

172.31.2.0/23

pod_cidr

Pod subnet CIDR

172.31.16.0/20

kube_client_cidr

CIDR for clients that are allowed to contact the Kubernetes API server

10.0.0.0/8

The IP Subnet Calculator on Calculator.net is one tool for finding all available networks for a given IP address and prefix length.