How to have External DNS manage a single A record that is always updated with all of the private IPs of the nodes in the cluster. #1928
-
|
I'm not sure where to ask this. It didn't seem to really be an issue, so I'm posting it here in discussions under Q&A. I want to configure External DNS to manage a single A record in a private zone in Route 53 that contains all the private IPs of all the nodes in my EKS cluster. I feel like this should be simple to do, but I've been searching the docs for at least a couple days and I'm not finding an answer. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
Of course, just after I decide to post a question, I find the answer. It turns out I just needed to use a service type of NodePort. I thought I had already tried that. Perhaps I was remembering that wrong, or I had some other parameters configured incorrectly. Maybe this will help someone else in the future. |
Beta Was this translation helpful? Give feedback.
-
|
does this actually work as intended? i am troubling atm with nodeport sind i would have expected the Route53 entry to route only to those IPs mapping my app-selector :/ |
Beta Was this translation helpful? Give feedback.
Of course, just after I decide to post a question, I find the answer. It turns out I just needed to use a service type of NodePort. I thought I had already tried that. Perhaps I was remembering that wrong, or I had some other parameters configured incorrectly. Maybe this will help someone else in the future.