Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

High level design for static egress configuration #1

Open
prateekgogia opened this issue Oct 15, 2018 · 0 comments
Open

High level design for static egress configuration #1

prateekgogia opened this issue Oct 15, 2018 · 0 comments

Comments

@prateekgogia
Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant