External-dns: On-Prem use single IP for each A record without using LoadBalancer manifest

[mitchellmaler]

We currently have CoreDNS on prem and using nginx to fo our load balancing for our cluster. We have a single F5 VIP (load balancing across the nginx) that we want each record to point too. Then using nginx to route to the correct ingress and server. So far I can tell you have to provide a LoadBalancer type but we do not use a cloud provider to do this. We would like all records point to that single VIP when users create a ingress.

[hjacobs]

@mitchellmaler that's easily possible, you don't need any service type LoadBalancer. Use the external-dns.alpha.kubernetes.io/target annotation on the Ingress object to point to your F5 VIP. See https://github.com/kubernetes-incubator/external-dns/blob/master/docs/faq.md#are-other-ingress-controllers-supported

[tonyfahrion]

Is there a way to persist the IP within external-dns or while doing the external-dns deployment? Changing every ingress resource is unhandy and forces each deployment to be environment aware and know the external IP. (I am just curious if there is a way - did not find a solution for this right now)

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[vbaidak]

Hi @tonyfahrion . Have you managed to configure external-dns to use single static ip by default?

[tonyfahrion]

Hi @tonyfahrion . Have you managed to configure external-dns to use single static ip by default?

Hi @vbaidak, no, we wrote an admission-controler to configure ingress resources automatically, so users don’t have to know the details.

[vbaidak]

thanks, @tonyfahrion

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[mrparkers]

@vbaidak not sure if you're still looking for something like this, but I also wrote an admission controller to assist with automatically adding the external-dns.alpha.kubernetes.io/target annotation to Ingresses and Istio VirtualServices. Feel free to use it directly, or as a reference for implementing your own.

https://github.com/mrparkers/external-dns-target-admission