You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tried using externalIPs but the controller still created the Cloudflare DNS record with an internal IP 192.168.1.10 and not the public IP 52.164.208.127.
❯ k get ing
NAME CLASS HOSTS ADDRESS PORTS AGE
vikas nginx vikas.example.com 192.168.1.10 80, 443 9d
What you expected to happen:
I expected the operator to create the DNS record with the public IP 52.164.208.127.
How to reproduce it (as minimally and precisely as possible):
Try using externalIPs in the helm values file.
Workaround
My workaround (after a few hours of Google-ing) was to add an annotation to the ingress external-dns.alpha.kubernetes.io/target: "52.164.208.127". Once, I updated the ingress resource with this annotation, the controller created the DNS record with the public IP.
Anything else we need to know?:
Environment:
External-DNS version (use external-dns --version): 8.6.0
What happened:
My kubernetes ingress defaults to the private IP of an internal load balancer. My setup looks like this
I tried using externalIPs but the controller still created the Cloudflare DNS record with an internal IP
192.168.1.10
and not the public IP52.164.208.127
.What you expected to happen:
I expected the operator to create the DNS record with the public IP
52.164.208.127
.How to reproduce it (as minimally and precisely as possible):
Try using externalIPs in the helm values file.
Workaround
My workaround (after a few hours of Google-ing) was to add an annotation to the ingress
external-dns.alpha.kubernetes.io/target: "52.164.208.127"
. Once, I updated the ingress resource with this annotation, the controller created the DNS record with the public IP.Anything else we need to know?:
Environment:
external-dns --version
): 8.6.0Linked Issues
The text was updated successfully, but these errors were encountered: