Save EKS IP Resources with Pod SNAT
Background Since the company-assigned VPC is an Intranet segment, used for interfacing with the local end, from the organization’s perspective, the VPC is not truly ‘Private’, therefore the IP quantity is still limited. Following the discovery that EKS Pods occupy ENIs, in order to solve this issue, I added another set of Private IP associated with the VPC, then performed a layer of translation via a Private NAT Gateway. This enables all EKS Pods to communicate with the local network segment through the same Intranet IP, achieving the goal of saving IP resources.