Creating route53 entries for pod IPs directly instead of loadbalancer/service


#1

Hi,

We are running an EKS cluster where pods get an IP address from the VPC IP range itself. We have an nginx running on virtual machines which are not running with K8S but are in the same VPC as the K8S cluster. We want to be able to route traffic from this nginx to services running in the K8S cluster. If we do this using an ingress, the packets go through multiple hops like the load balancer, kube-proxy before reaching to the pod. Since these particular applications don’t scale and pods have an IP which is routable inside VPC, we could just create an entry in Route53 for this pod and be done. However someone needs to update Route53 if the pod IP changes. Do I need to write my own ingress controller to do this? Can I leverage any existing solution like external-dns?