The easiest way to control the egress IP of a set of pods is to use VPC CNI Custom Networking along with a NAT Gateway.
In the VPC, designate one or more separate internal subnets (ideally one per AZ) in which only these pods live. (There's just no practical way to do this without reserving a subnet.) Create the appropriate ENIConfig CRD to map these pods to the subnets. Then, in one or more separate public subnets in the same AZ, create a NAT Gateway, using a pre-created Elastic IP as its IP address. Create a default route from the each internal subnet to the NAT Gateway in the same AZ.
FSx for Windows EKS Nodesasked 2 months ago
EKS Node Group with RIAccepted AnswerEXPERTasked 2 years ago
EKS Node Group Strategyasked 3 months ago
EKS VPC-CNI Plugin Node Group Setup Questionsasked 7 months ago
How EKS Control Plane is communicate with worker nodeasked a year ago
Difference between EKS managed node group and self-managed node groupAccepted Answerasked 17 days ago
How to create EKS cluster with dedicated host node groupAccepted Answerasked a year ago
EKS static IPs for managed node group nodesAccepted Answerasked 2 years ago
EKS Managed Node Groups - PodEvicitionFailureasked 3 years ago
How to remove a specific node from EKS node group (none managed eksctl)Accepted Answerasked 4 months ago