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 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...
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?
The text was updated successfully, but these errors were encountered:
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?
The text was updated successfully, but these errors were encountered: