Problem viewing routes on Linkerd Dashboard and how to check if Linkerd is Encrypting the routes

[nikhilcreddy]

I have installed linkerd, linkerd-viz and emojivoto demo app in my AKS kubernetes cluster. Also Injected Linked to emojivoto namespace. I can access emojivoto application by port forwarding, but why don't I see the routes like shown in the Linkerd getting started page like .

The below image is what I see. Is there a way I could see all the incoming and outgoing routes a service has through the dashboard.

Is Linkerd encrypting all the routes between meshed services?
if yes, how can I know if the route is encrypted.

Thank you!

[olix0r]

The linkerd viz edges command should be able to display what other pods a workload communicates with and whether that communication is using TLS. I believe this information is also available via the web UI if you scroll down :)

[kleimkuhler]

@NikhilChandraReddy You should see edges between web/emoji, web/voting, and vote-bot/web. Could you provide the output for linkerd check --proxy? It's possible something is wrong between those deployments which is why it seems like there is no traffic between them.

[nikhilcreddy]

@kleimkuhler, after running linkerd check --proxy below is what I get, looks like every thing is fine.

 linkerd check --proxy                                                                                                                                                                                                    kubernetes-api
--------------
√ can initialize the client
√ can query the Kubernetes API

kubernetes-version
------------------
√ is running the minimum Kubernetes API version
√ is running the minimum kubectl version

linkerd-existence
-----------------
√ 'linkerd-config' config map exists
√ heartbeat ServiceAccount exist
√ control plane replica sets are ready
√ no unschedulable pods
√ controller pod is running

linkerd-config
--------------
√ control plane Namespace exists
√ control plane ClusterRoles exist
√ control plane ClusterRoleBindings exist
√ control plane ServiceAccounts exist
√ control plane CustomResourceDefinitions exist
√ control plane MutatingWebhookConfigurations exist
√ control plane ValidatingWebhookConfigurations exist
√ control plane PodSecurityPolicies exist

linkerd-identity
----------------
√ certificate config is valid
√ trust anchors are using supported crypto algorithm
√ trust anchors are within their validity period
√ trust anchors are valid for at least 60 days
√ issuer cert is using supported crypto algorithm
√ issuer cert is within its validity period
√ issuer cert is valid for at least 60 days
√ issuer cert is issued by the trust anchor

linkerd-webhooks-and-apisvc-tls
-------------------------------
√ proxy-injector webhook has valid cert
√ proxy-injector cert is valid for at least 60 days
√ sp-validator webhook has valid cert
√ sp-validator cert is valid for at least 60 days

linkerd-identity-data-plane
---------------------------
√ data plane proxies certificate match CA

linkerd-api
-----------
√ control plane pods are ready
√ can initialize the client
√ can query the control plane API

linkerd-version
---------------
√ can determine the latest version
√ cli is up-to-date

linkerd-data-plane
------------------
√ data plane namespace exists
√ data plane proxies are ready
‼ data plane is up-to-date
    Some data plane pods are not running the current version:
        * emoji-5bc49bf464-zjqzn (stable-2.10.1)
        * vote-bot-7b8bff96c7-xjjlp (stable-2.10.1)
        * voting-7fc8b496d7-4fbq7 (stable-2.10.1)
        * web-74df8f57d7-2x6wp (stable-2.10.1)
        * grafana-5b6cd99f6b-x4r8b (stable-2.10.1)
        * metrics-api-6474d5ff89-b5p9k (stable-2.10.1)
        * prometheus-57686fbdfd-sbqp8 (stable-2.10.1)
        * tap-74bbf6c55f-w8h8r (stable-2.10.1)
        * tap-injector-7ff4dc9b96-rwxx4 (stable-2.10.1)
        * web-6f75bd5746-2tvhn (stable-2.10.1)
        * linkerd-controller-5475cfbff7-pc9md (stable-2.10.1)
        * linkerd-destination-6f9fd64bff-jsb5g (stable-2.10.1)
        * linkerd-identity-6847c77645-kjlnm (stable-2.10.1)
        * linkerd-proxy-injector-cd4996458-px726 (stable-2.10.1)
        * linkerd-sp-validator-7db8b859f-q6p76 (stable-2.10.1)
    see https://linkerd.io/2.10/checks/#l5d-data-plane-version for hints
‼ data plane and cli versions match
    <--------> running stable-2.10.1 but cli running stable-2.10.2
    see https://linkerd.io/2.10/checks/#l5d-data-plane-cli-version for hints

Status check results are √

Linkerd extensions checks
=========================

                              linkerd-viz
-----------
√ linkerd-viz Namespace exists
√ linkerd-viz ClusterRoles exist
√ linkerd-viz ClusterRoleBindings exist
√ tap API server has valid cert
√ tap API server cert is valid for at least 60 days
√ tap API service is running
√ linkerd-viz pods are injected
√ viz extension pods are running
√ prometheus is installed and configured correctly
√ can initialize the client
√ viz extension self-check

linkerd-viz-data-plane
----------------------
√ data plane namespace exists
√ data plane proxy metrics are present in Prometheus

Status check results are √

[kleimkuhler]

Do you have any output with the stat command? On a cluster where I see edges between emojivoto deployments I have the following:

$ linkerd viz stat -n emojivoto deployment
NAME       MESHED   SUCCESS      RPS   LATENCY_P50   LATENCY_P95   LATENCY_P99   TCP_CONN
emoji         1/1   100.00%   2.3rps           1ms           1ms           1ms          3
vote-bot      1/1   100.00%   0.3rps           1ms           1ms           1ms          1
voting        1/1    92.21%   1.3rps           1ms           1ms           1ms          3
web           1/1    95.59%   2.3rps           3ms           5ms           9ms          3

[nikhilcreddy]

Hi @kleimkuhler , with the stat command I see the same output as yours.

>>> linkerd viz stat -n emojivoto deployment
NAME       MESHED   SUCCESS      RPS   LATENCY_P50   LATENCY_P95   LATENCY_P99   TCP_CONN
emoji         1/1   100.00%   2.3rps           1ms           1ms           1ms          3
vote-bot      1/1   100.00%   0.3rps           1ms           1ms           1ms          1
voting        1/1    89.47%   1.3rps           1ms           1ms           1ms          3
web           1/1    92.65%   2.3rps           2ms           4ms           5ms          3

[ronocg]

@NikhilChandraReddy did you get this resolved I am just after deploying linkerd on AKS and have the same issue as outlined here ?