IP Address Pools

Comprehensive Network Allocation View
🖥️
Node Network
10.0.0.0/16
Physical/virtual infrastructure addresses. These IPs are routable on the corporate network.
Gateway
10.0.1.1
Default route to external network
Node 1
10.0.1.10
Worker node physical interface
Node 2
10.0.1.11
Worker node physical interface
Node 3
10.0.1.12
Worker node physical interface
📦
Pod Network
10.128.0.0/14
Overlay network for pod-to-pod communication. Each node gets a /23 subnet.
Node 1 Pod Subnet
10.128.0.0/23
510 usable IPs
Example Pod on Node 1
10.128.0.5
Ephemeral, changes on restart
Node 2 Pod Subnet
10.128.2.0/23
510 usable IPs
Example Pod on Node 2
10.128.2.10
Ephemeral, changes on restart
Node 3 Pod Subnet
10.128.4.0/23
510 usable IPs
⚖️
Service Network
172.30.0.0/16
Virtual IPs for stable service endpoints. Never assigned to physical interfaces.
web-frontend Service
172.30.45.100
Load balances to 3 frontend pods
api-backend Service
172.30.50.200
Load balances to 5 API pods
database Service
172.30.60.55
Load balances to 1 database pod
kube-dns (CoreDNS)
172.30.0.10
Cluster DNS resolution service
Key Architectural Points
No CIDR Overlap: Three completely separate address spaces prevent routing conflicts
Pod IPs are Ephemeral: Pods get new IPs on restart - use Services for stability
Service IPs Never Leave Cluster: Virtual IPs exist only in iptables/OVN rules
Node IPs are Infrastructure: Routable on corporate network, used for management and ingress
Per-Node Pod Subnets: Each node gets a /23 (510 IPs) from the pod network pool
Overlay Network Routing: Pod traffic tunneled (Geneve) between nodes via node IPs