'Simplest way to setup egress gateway with EKS without Istio
How can I setup an egress gateway so that all traffic outbound from an EKS cluster has a single external IP? I need to do this to comply to corporate policies relating to incoming IPs when accessing external services outside the cluster. We are currently adding node IPs (for nodes with public IP) and NAT gateway IP (for private nodes) manually to the allowed range but it is getting more and more painful due to dynamically spinned up nodes by Karpenter.
Currently, we are using Kong to control ingress traffic, so Istio is not a choice.
amazon-web-servicesSources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow
| Solution | Source |
|---|