Hybrid Nodes Prerequisites and Routing

Hybrid Nodes Prerequisites and Routing An architecture diagram generated by Archify. EKS cluster configuration · RemoteNodeNetwork 10.80.0.0/16 · RemotePodNetwork 10.85.0.0/16 · AWS Region EKS cluster configuration RemoteNodeNetwork 10.80.0.0/16 · RemotePodNetwork 10.85.0.0/16 VPC 10.226.0.0/16 · Subnets · route table · AWS Region VPC 10.226.0.0/16 Subnets · route table Private connectivity · Direct Connect · VPN (gateway ↔ on-prem gateway) · Architecture component Private connectivity Direct Connect · VPN (gateway ↔ on-prem gateway) On-prem router · On-prem routing table · On-prem environment On-prem router On-prem routing table Hybrid nodes 1 · 2 · Nodes 10.80.0.0/16 · pods 10.85.1.0/24, 10.85.2.0/24 · On-prem environment Hybrid nodes 1 · 2 Nodes 10.80.0.0/16 · pods 10.85.1.0/24, 10.85.2.0/24 declares remote CIDRs remote CIDRs both ways per-node pod routes AWS Region On-prem environment Legend Backend Cloud Message bus

VPC route table

  • • 10.80.0.0/16 → Gateway (remote node range)
  • • 10.85.0.0/16 → Gateway (remote pod range)
  • • 10.226.0.0/16 → local (the VPC's own range)

On-prem routing table

  • • 10.85.1.0/24 → hybrid node 1
  • • 10.85.2.0/24 → hybrid node 2
  • • 10.226.0.0/16 → on-prem gateway (toward the VPC)

Requirements at a glance

  • • RemoteNodeNetwork and RemotePodNetwork are set at cluster creation and must not overlap the VPC CIDR
  • • Nodes can be bare metal or virtualized hosts and take IPs from the node range
  • • Pod traffic works only when both routing tables know the other side's range