Skip to content
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

Inherited a non standard ingress setup... can External DNS support this? #5121

Open
vchan2002 opened this issue Feb 24, 2025 · 0 comments
Open
Labels
kind/support Categorizes issue or PR as a support question.

Comments

@vchan2002
Copy link
Contributor

I have inherited a setup that is similar to the public and private route setup, along with two nginx ingress controllers, one for private and one for public...

https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/aws-public-private-route53.md

But with a twist....

While the private one is setup with a type of Load Balancer, and that's fine, and I think I can figure that part out.......

However, the pubilc one is setup as a Nodetype service, so the these external hosts names is mapped to an IP in the 172.20.0.0 range. The actual ingress to this public nginx ingress is an ALB load balancer controller setup with the backend service set to the nodetype service specified to the in the public nginx ingress controller..... and its hosts is setup as a wildcard to our domain.

Would ExternalDNS be smart enough to figure this out and map those public facing DNS names to the ALB, ie the ingress to the public nginx ingress?

@vchan2002 vchan2002 added the kind/support Categorizes issue or PR as a support question. label Feb 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/support Categorizes issue or PR as a support question.
Projects
None yet
Development

No branches or pull requests

1 participant