Ambassador qotm route shows "no healthy upstream"

General Discussions
21

thanks for the reply - I jkust tried now with WeaveNet. with this the DNS is accessbiel and now the issues turns to be:
/ # nslookup kubernetes.default
Server: 10.96.0.10
Address: 10.96.0.10:53

** server can’t find kubernetes.default: NXDOMAIN

*** Can’t find kubernetes.default: No answer

/ # nslookup qotm.default
Server: 10.96.0.10
Address: 10.96.0.10:53

** server can’t find qotm.default: NXDOMAIN

*** Can’t find qotm.default: No answer
: I would like to know how you got to work this out without an overlay!

22

Does that service exist (kubernetes.default)?

One problem is if you get intermittent failures, but another is if it never resolves. Which is your case now?

Before you were using an IP address, right? Why aren’t you using one now?

23

interestingly. with Weave Net, I am able to do From: BusyBox > wget qotm works, the nslookup fails (which I feel trivial for now) though. But there is this ambassador ingress which fails for the same qotm access. the /etc/resolv.conf of ambassador pod shows the exact copy of NODE’s resolv.conf.

24

@rata now with the new setup; i observed that resolv.conf in pods differs.
on qotm service - /service # cat /etc/resolv.conf
nameserver 172.30.96.86
nameserver 172.30.96.80
nameserver 192.168.1.1
search ent.bhicorp.com

But in busy box : / # cat /etc/resolv.conf
nameserver 10.96.0.10
search default.svc.cluster.local. svc.cluster.local. cluster.local. ent.bhicorp.com
options ndots:5

Any idea as to how to solve this

25

@rata -thanks for helping.
Now it is all working with Kube 1.14.0 and weave net as CNI. Also, I corrected my ambassador spec to be dnsPolicy : ClusterFirst.
The DNS lookup based on service name is working as of now.

26

Awesome! It was hard but finally working!

The problem was the CNI, then? And you changed it to solve it? Please share so we all learn :slight_smile:

27

Ah Yes the issue appears to be with the CNI. I think something tricky to be applied while using Flannel (still unknown for me). But with Weave Net it just worked like a charm.

28

Thanks! :slight_smile: