Linkerd exceptions

Help Kubernetes
#1

Hi, I am trying to run linkerd with kubernetes as daemonset. I am exposing it’s service as Nodeport. I am facing some issues with linkerd. like linkerd dashboard don’t show any services which are registered …etc

Here is list of exceptions:

Can someone help me in understanding them.

curl 100.x.x.85:30395/admin/metrics.json?pretty=1 | jq ‘with_entries(select(.key | contains(“failure”), contains(“exception”)))’

{
“namer/#/io.l5d.k8s/client/failure_accrual/probes”: 0,
“namer/#/io.l5d.k8s/client/failure_accrual/removals”: 0,
“namer/#/io.l5d.k8s/client/failure_accrual/removed_for_ms”: 0,
“namer/#/io.l5d.k8s/client/failure_accrual/revivals”: 0,
“rt/incoming/server/0.0.0.0/4141/failures”: 284,
“rt/incoming/server/0.0.0.0/4141/failures/com.twitter.finagle.service.ResponseClassificationSyntheticException”: 284,
“rt/incoming/service/svc/100.99.17.14:31634/failures”: 99,
“rt/incoming/service/svc/100.99.17.14:31634/failures/com.twitter.finagle.NoBrokersAvailableException”: 99,
“rt/incoming/service/svc/100.99.17.14:31634/sourcedfailures//svc/100.99.17.14:31634”: 99,
“rt/incoming/service/svc/100.99.17.14:31634/sourcedfailures//svc/100.99.17.14:31634/com.twitter.finagle.NoBrokersAvailableException”: 99,
“rt/incoming/service/svc/100.99.19.1:31634/failures”: 99,
“rt/incoming/service/svc/100.99.19.1:31634/failures/com.twitter.finagle.NoBrokersAvailableException”: 99,
“rt/incoming/service/svc/100.99.19.1:31634/sourcedfailures//svc/100.99.19.1:31634”: 99,
“rt/incoming/service/svc/100.99.19.1:31634/sourcedfailures//svc/100.99.19.1:31634/com.twitter.finagle.NoBrokersAvailableException”: 99,
“rt/incoming/service/svc/100.99.22.18:31634/failures”: 86,
“rt/incoming/service/svc/100.99.22.18:31634/failures/com.twitter.finagle.NoBrokersAvailableException”: 86,
“rt/incoming/service/svc/100.99.22.18:31634/sourcedfailures//svc/100.99.22.18:31634”: 86,
“rt/incoming/service/svc/100.99.22.18:31634/sourcedfailures//svc/100.99.22.18:31634/com.twitter.finagle.NoBrokersAvailableException”: 86,
“rt/outgoing/server/0.0.0.0/4140/failures”: 280,
“rt/outgoing/server/0.0.0.0/4140/failures/com.twitter.finagle.service.ResponseClassificationSyntheticException”: 280,
“rt/outgoing/service/svc/100.99.17.14:31257/failures”: 101,
“rt/outgoing/service/svc/100.99.17.14:31257/failures/com.twitter.finagle.NoBrokersAvailableException”: 101,
“rt/outgoing/service/svc/100.99.17.14:31257/sourcedfailures//svc/100.99.17.14:31257”: 101,
“rt/outgoing/service/svc/100.99.17.14:31257/sourcedfailures//svc/100.99.17.14:31257/com.twitter.finagle.NoBrokersAvailableException”: 101,
“rt/outgoing/service/svc/100.99.19.1:31257/failures”: 95,
“rt/outgoing/service/svc/100.99.19.1:31257/failures/com.twitter.finagle.NoBrokersAvailableException”: 95,
“rt/outgoing/service/svc/100.99.19.1:31257/sourcedfailures//svc/100.99.19.1:31257”: 95,
“rt/outgoing/service/svc/100.99.19.1:31257/sourcedfailures//svc/100.99.19.1:31257/com.twitter.finagle.NoBrokersAvailableException”: 95,
“rt/outgoing/service/svc/100.99.22.18:31257/failures”: 84,
“rt/outgoing/service/svc/100.99.22.18:31257/failures/com.twitter.finagle.NoBrokersAvailableException”: 84,
“rt/outgoing/service/svc/100.99.22.18:31257/sourcedfailures//svc/100.99.22.18:31257”: 84,
“rt/outgoing/service/svc/100.99.22.18:31257/sourcedfailures//svc/100.99.22.18:31257/com.twitter.finagle.NoBrokersAvailableException”: 84,
“rt/outgoing/transformer/%/io.l5d.k8s.daemonset/default/incoming/l5d/client/failure_accrual/probes”: 0,
“rt/outgoing/transformer/%/io.l5d.k8s.daemonset/default/incoming/l5d/client/failure_accrual/removals”: 0,
“rt/outgoing/transformer/%/io.l5d.k8s.daemonset/default/incoming/l5d/client/failure_accrual/removed_for_ms”: 0,
“rt/outgoing/transformer/%/io.l5d.k8s.daemonset/default/incoming/l5d/client/failure_accrual/revivals”: 0
}

#2

Hi @amolsh,

Under most configurations, Linkerd routes based on the Host header. Try sending requests to Linkerd that have the Host header set to the service that you want to talk to:

curl $LINKERD:4140 -H "Host: foo"

or

http_proxy=$LINKERD:4140 curl foo
#3

Hi @amolsh. Any luck getting this to work?

#4

Yep, We followed little different approach and it worked. Thanks.

#5

Awesome, glad to hear it!