Closed prasenforu closed 7 years ago
Hey @prasenforu, thanks for reporting. This sounds like a duplicate of linkerd/linkerd#1347. If linkerd is unable to route the request, then it also won't show up in the zipkin ui. If linkerd can't connect to zipkin, then you'll see errors in the logs that look like this:
I 0707 20:02:06.374 UTC THREAD111 TraceId:77689a2c404454a5: FailureAccrualFactory marking connection to "zipkin-tracer" as dead. Remote Address: Inet(localhost/127.0.0.1:1463,Map())
Absent those errors, then I think the issue is the fact that linkerd needs additional RBAC privileges to route within your cluster. There are a few suggestions of how to fix in linkerd/linkerd#1347.
Thanks 😀
Env : kubernetes 1.7.0
Using linkerd-zipkin yml file (https://github.com/linkerd/linkerd-examples/blob/master/k8s-daemonset/k8s/linkerd-zipkin.yml)
oc get all output in default namespace:
output of pod (l5d -container) logs (root@ip-172-31-29-6:~oc logs -f po/l5d-f8193 l5d)
looks like services are not discovered by linkerd pod
by searching url (https://github.com/linkerd/linkerd/issues/1347) error gone
but NO tracing in zipkin :( but in linkerd admin console I am getting incoming/outgoing data.
Not sure if zipkins required cluster role binding ?
Please help