Issue with externalname #2769
Replies: 3 comments 3 replies
-
@whitakersp-fineos Hello there. |
Beta Was this translation helpful? Give feedback.
-
@whitakersp-fineos great.
|
Beta Was this translation helpful? Give feedback.
-
I noticed that you mentioned you are setting KubeDNS as the resolver. I bring this up as it is common in public clouds that KubeDNS is integrated with external DNS resolution, but in other cases it is not. |
Beta Was this translation helpful? Give feedback.
-
Hey. there, i'm trying to setup an ingress for an external url and I'm following the very light instructions here, https://github.com/nginxinc/kubernetes-ingress/tree/v2.2.2/examples/externalname-services.
Here's my setup.
I added the
resolver-address
to my configmap and set that to the cluster-ip of kube-dns.Problem is when I look at the
/etc/nginx/conf.d/generetedfile.conf
I see my location route and the upstream it created, but the up stream is missing any kind of server information for what i'm proxying, and i get a 502 error and the logs of course say no live upstreams found.Here's what is generated
Any idea what i'm doing wrong here?
Beta Was this translation helpful? Give feedback.
All reactions