<p>I'm using OVH cloud and K8S (with ingress/loadbalancer/nginx)</p>
<p>How can I route all my node traffic (my containers) to ingress (Loadbalancer)? Actually I got one Public IP by Node, (and they change every time I setup/delete node)</p>
<p><strong>The Goal</strong> : have always same public IP when I request external API, I need trust my IP to this external API (by white list)</p>
<p>I looked about <code>Egress</code> but is look it's not work.</p>
<p>Have you some example or tips for me?</p>

<p>You can proxy container or proxy DNS option with each running pod which will pass the traffic to specific DNS pod and that will manage your traffic from one single Node.</p>
<p>However it's not scalable solution.</p>
<p>If you are using the <strong>istio</strong> also thn also you have to create the Egress gateway POD fix on a single node with <strong>affinity</strong>. So each time you will get the same IP if the container <strong>restart</strong> or so and get back scheduled to same node.</p>
<p><a href="https://istio.io/latest/docs/tasks/traffic-management/egress/egress-gateway/" rel="nofollow noreferrer">https://istio.io/latest/docs/tasks/traffic-management/egress/egress-gateway/</a></p>
<p>Another solution is to use the NAT gateway i have not setup with OVH cloud however it's scalable solution if you Node are in public subnet.</p>
<p>Here is nice GKE project we been using to create single point of egress for our K8s clusters : <a href="https://github.com/GoogleCloudPlatform/terraform-google-nat-gateway/tree/v1.2.3/examples/gke-nat-gateway" rel="nofollow noreferrer">https://github.com/GoogleCloudPlatform/terraform-google-nat-gateway/tree/v1.2.3/examples/gke-nat-gateway</a></p>
<p>You can also implement same with OVH cloud if you can using the NAT gateway.</p>
