I'm trying to use external-dns with a bare metal load balancer. I tried using metallb as the kubernetes load balancer, but the IP address assigned in the A record is the internal IP address of the load balancer, rather than than the public IP address of the load balancer. According the to the external-dns docs, if status.loadBalancer is empty (which it will always be), external-dns would not work as expected even though I have set the external IP for the service.
Asked
Active
Viewed 431 times
0
charlesreid1
- 4,360
- 4
- 30
- 52
Josh Woodcock
- 2,683
- 1
- 22
- 29
-
what k8s version are you using? – Matt Dec 13 '19 at 14:30
-
I am using version 1.14.7 – Josh Woodcock Dec 21 '19 at 17:41
-
would you like to create records based on Ingresses, Services or any other resource types? – Bernard Halas Apr 20 '21 at 13:14
1 Answers
0
external-dns needs to become aware of the IP address of the loadbalancer. If the status.loadbalancer field is empty, one way how to make external-dns aware of the correct IP is to use the annotation external-dns.alpha.kubernetes.io/target: "<metalLB-vip>"
Bernard Halas
- 972
- 11
- 24