amazon-vpc-cni-k8s
amazon-vpc-cni-k8s copied to clipboard
eks with secondary network for pods
Following the documentation, we end up in the following scenario. https://aws.github.io/aws-eks-best-practices/networking/custom-networking/
The pod receives the IPs from the secondary subnet and to try to access resources outside the VPC, the main IP of the node in the main network is used, but for resources in the same VPC it tries to use the secondary IP that the pod receives. Is there a way to mask the pod IP to the main IP for internal resources in the same VPC?
pod ip: 100.127.35.58 node ip: 192.168.1.44
when trying to access an RDS resource in the same vpc the pod uses the ip 100.127.35.58
to access a resource outside the vpc a masking is done so that the pod uses the node ip 192.168.1.44
We would like this masking to also be done for internal resources in the same VPC