4 ms·
In my experience NAT is almost always involved in a Kubernetes setup (for on-prem). The container network is generally not routable to the wider corporate WAN
by raesene9 9y ago
In my experience NAT is almost always involved in a Kubernetes setup (for on-prem).
The container network is generally not routable to the wider corporate WAN (it'll use RFC1918 addresses by default). You typically get one set of addresses for the main container network, a different set of addresses for the service IPs and then an routable set on the ingress.
- zaat 9y agoWhat you describe is not NAT, the containers network segment is a separate network segment which is not accessible from outside the cluster, not directly and not through address translation. The ingress and service addresses are externally reachable addresses that expose services. NAT is not required for the setup.
- raesene9 9y agoIf traffic flows from the pod network to an external network NAT is involved, as the Pod network is not routable.
- puzzle 9y agoI can see how it's more likely on prem, but at my job, we run Kubernetes in production on AWS and most traffic is pod to pod, without NAT involved.