-
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
Question: how to specify a custom hostname for ingress #450
Labels
kind/support
Categorizes issue or PR as a support question.
Comments
Did you try the
annotation as well? |
Is there a way to specify multiple hostnames for case when you have virtual hosting type of Ingress behind ELB? |
I just found PR #256 and the answer is YES, just use
|
lou-lan
pushed a commit
to lou-lan/external-dns
that referenced
this issue
May 11, 2022
This came up in kubernetes-sigs/krew-index#407. We don't currently release krew for linux/arm64, but apparently linux/arm distribution we have works there. This would allow plugins to be distributed for linux/arm64, in addition to existing linux/arm. Signed-off-by: Ahmet Alp Balkan <ahmetb@google.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I need to put a Cloudfront distribution in front of my Ingress Controller ELB and wonder if there is a way to have external-dns use the Cloudfront distribution hostname (so let's say it's an arbitrary static value) for the Ingress endpoint instead of the Ingress ELB endpoint. In this case, I have one backend per ingress so I can use a global annotation. In fact, I have a dedicated Ingress Controller and external-dns instance so I can even use a global value for all the endpoints.
I tried to use the external-dns.alpha.kubernetes.io/target and the --fqdn-template parameter without success, so I hope I'm missing something :)
Thanks
The text was updated successfully, but these errors were encountered: