You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I validated the approach by running a POD in a Kubernetes cluster and configuring IPTABLES rules to do DNAT and SNAT inside this POD. A NAT pod will have a one-to-one mapping to a backend service to keep it simple to start with, later a single NAT gateway may forward traffic to multiple backend services. Now any traffic coming in to this NAT gateway gets forwarded to the backend application with source IP as a VIP IP configured as secondary IP on this pods interface (eth0:0).
Please provide feedback and we can discuss this in our next meeting.
The text was updated successfully, but these errors were encountered:
Hi
I validated and documented the second approach I was talking about for running NAT gateway as a POD, here
https://docs.google.com/document/d/1usUZQ6q3o9n23IH7iOF6OSa4BvaZidnBTj5tj-o-8Ks/edit#heading=h.2q2h912eh0x2
I validated the approach by running a POD in a Kubernetes cluster and configuring IPTABLES rules to do DNAT and SNAT inside this POD. A NAT pod will have a one-to-one mapping to a backend service to keep it simple to start with, later a single NAT gateway may forward traffic to multiple backend services. Now any traffic coming in to this NAT gateway gets forwarded to the backend application with source IP as a VIP IP configured as secondary IP on this pods interface (eth0:0).
Please provide feedback and we can discuss this in our next meeting.
The text was updated successfully, but these errors were encountered: