-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
external-dns with a Traefik 2.0 IngressRoute #2286
Comments
@alysonfranklin Have you checked: Which Service and Ingress controllers are supported? #1257: Is it possible to use external-dns with a Traefik 2.0 IngressRoute resource? #1299: How to handle traefik2 new CRD's ingressroute and ingressroutetcp #413: Support Traefik ingress controller |
Workaround proposed on traefik/traefik#4655 works fine when there is just one copy of Traefik running but on multi-tenant K8s cluster with multiple Traefik instances those KubernetesIngress providers looks to be fighting about same resources and end up to CPU 100% which I have not see with KubernetesCRD configuration when allowcrossnamespace=false Is someone working on to get Traefik IngressRoute support included to external-dns? |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
Let's keep this open for now (until there's an accepted solution from either traefik or external-dns). /remove-lifecycle stale |
I can confirm, when using traefik v2.6 as ingress controller set the value |
Hello everyone , anyone has any luck to solve this issue ? |
Here the same problem :( |
Im also having no luck with Traefik 2.6.3 and External-DNS 0.12.0 Traefik is configured as:
The ingressroute for my app:
but external-dns is never finding anything to do:
I dont have I also know the ingressroute/service are working as expected:
Not sure what else there is to troubleshoot to get external-dns to pick up the DNS to generate I even tried using a
|
Somehow it seems to have gone under here, but this issue keeps popping up in my notifications. I created and maintain multiple clusters with Traefik and external-dns and it works fine when simply using the default In the end the Traefik CRDs are just a "nicer" instead of using annotations, but if that many people really want to use them it's easy to support them: implement the required logic to support it. Many CRDs of popular controllers are supported that can be found in the This issue keeps popping up and whenever I check it I see a new comment about how it does not work with a Traefik CRD, but exactly this is the topic of this issue and this is not a bug but simply a unsupported use case. This should not sound rude, but please always make sure to read a whole issue before posting (even when there are many comments), otherwise you keep pinging many others that watch this issue for information that are still not relevant to find a solution. There is also #1257 and some weeks ago a user posted a comment (not @-mention him to prevent notification noise) about his Footnotes |
Your explanation about IngressTCP is actually very helpful. However: you can unsubscribe from this issue if you feel like an open issue is bothering you with notifications. For what its worth I did read this entire issue and your explanation is the first here to explain the core problem. I did find switchboard and have been digging in to see if it helps translate from |
Yeah, the Regarding the issue notifications: sure, unsubscribing is always a way, but then I will also miss possible replies from the maintainers about updates or possible solutions (release announcement etc.). And you're right, I've mistaken this issue with #1257 which contains tons of comments, this one is small and (due to the higher number) also a duplicate, but I always sub to all open issues to not miss solutions. Let's try to keep the conversation in #1257 to not cause any more sub-noise here 😉 |
Hi @svengreb im trying to ise Ingress type with work with traefik ingress and external-dns. Is there an example of yaml that i can use ? |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /close not-planned |
@k8s-triage-robot: Closing this issue, marking it as "Not Planned". In response to this:
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. |
@svengreb You do not seem to know exactly all use cases. I do have a use case where I cannot - as far as I know yet - use Ingress and need to use IngressRoute instead. I have oauth2-proxy running as a standalone app in its own namespace, separated from everything else. I have an app that I would like to secure using Keycloak through oauth2-proxy. The app has its own namespace too. Traefik itself as well. So I have
Now if I want to add an ingress rule for / that points to the app's service and another rule /oauth2/ that points to oauth2-proxy service, I need a way to use Ingress accross namespace borders. I could use an ExternalName, but that would require me to allow ExternalName services, which I haven't yet. Multiple Ingress objects pointing to the same host are not allowed as it seems. I also seem to need different Middlewares for each path prefix. So there's
which IngressRoute afaik supports but Ingress does not. So, yeah, there are use cases which Ingress does not cover. That's why I would love ExternalDNS to support IngressRoute too. In the meantime, of course I could use switchboard. But that's another component that adds to the complexity and another workload for my cluster. If you see other solutions to my problem, don't hesitate to teach me! I'm merely a K8s novice. |
@HWiese1980 Since #3055 has been merged, and is available as of version 0.13.6, there is no need to use any workarounds anymore, it is now officially supported. |
Documentation for traefik if someone is looking is available here: README format: https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/traefik-proxy.md HTML format: https://kubernetes-sigs.github.io/external-dns/latest/tutorials/traefik-proxy/ Please take into account that |
I was able to use external-dns with AWS Route53 and EKS cluster with a Traefik 1.7 Ingress resource, but have been unable to achieve the same with the Traefik 2.0 IngressRoute resource. I have annotated my service to provide the hostname information.
Of course, my.awesome.domain.com is not my real domain, but is unimportant.
Does external-dns require a Kubernetes Ingress? If not how might I get it to work with a new CRD type, such as the Traefik 2.0 IngressRoute?
Many thanks in advance!
The text was updated successfully, but these errors were encountered: