"No data to display" on live calls for deployment

[donkodimov]

Bug Report

What is the issue?

On getting started with linkerd I am facing an issue with live calls on the UI. Live calls for a deployment web are not displayed. Running linkerd top deployment/web --namespace emojivoto on the console is displaying the data.

How can it be reproduced?

Run the steps from https://linkerd.io/2/getting-started/

Logs, error output, etc

When open http://dashboard.example.com/namespaces/emojivoto/deployments/web I see:

Websocket error: undefined

linkerd check output

--------------
√ 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
√ can initialize the client
√ can query the control plane API

linkerd-config
--------------
√ control plane Namespace exists
√ control plane ClusterRoles exist
√ control plane ClusterRoleBindings exist
√ control plane ServiceAccounts exist
W1120 10:43:30.771595   17174 warnings.go:67] apiextensions.k8s.io/v1beta1 CustomResourceDefinition is deprecated in v1.16+, unavailable in v1.22+; use apiextensions.k8s.io/v1 CustomResourceDefinition
√ control plane CustomResourceDefinitions exist
W1120 10:43:30.793950   17174 warnings.go:67] admissionregistration.k8s.io/v1beta1 MutatingWebhookConfiguration is deprecated in v1.16+, unavailable in v1.22+; use admissionregistration.k8s.io/v1 MutatingWebhookConfiguration
√ control plane MutatingWebhookConfigurations exist
W1120 10:43:30.805300   17174 warnings.go:67] admissionregistration.k8s.io/v1beta1 ValidatingWebhookConfiguration is deprecated in v1.16+, unavailable in v1.22+; use admissionregistration.k8s.io/v1 ValidatingWebhookConfiguration
√ 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
-------------------------------
√ tap API server has valid cert
√ tap API server cert is valid for at least 60 days
W1120 10:43:30.869434   17174 warnings.go:67] admissionregistration.k8s.io/v1beta1 MutatingWebhookConfiguration is deprecated in v1.16+, unavailable in v1.22+; use admissionregistration.k8s.io/v1 MutatingWebhookConfiguration
√ proxy-injector webhook has valid cert
√ proxy-injector cert is valid for at least 60 days
W1120 10:43:31.100244   17174 warnings.go:67] admissionregistration.k8s.io/v1beta1 ValidatingWebhookConfiguration is deprecated in v1.16+, unavailable in v1.22+; use admissionregistration.k8s.io/v1 ValidatingWebhookConfiguration
√ sp-validator webhook has valid cert
√ sp-validator cert is valid for at least 60 days

linkerd-api
-----------
√ control plane pods are ready
√ control plane self-check
√ [kubernetes] control plane can talk to Kubernetes
√ [prometheus] control plane can talk to Prometheus
√ tap api service is running

control-plane-version
---------------------
√ control plane is up-to-date
√ control plane and cli versions match
W1120 10:43:32.095952   17174 warnings.go:67] admissionregistration.k8s.io/v1beta1 MutatingWebhookConfiguration is deprecated in v1.16+, unavailable in v1.22+; use admissionregistration.k8s.io/v1 MutatingWebhookConfiguration

linkerd-prometheus
------------------
√ prometheus add-on service account exists
√ prometheus add-on config map exists
√ prometheus pod is running

linkerd-grafana
---------------
√ grafana add-on service account exists
√ grafana add-on config map exists
√ grafana pod is running

Status check results are √

Environment

• Kubernetes Version: Major:"1", Minor:"19", GitVersion:"v1.19.0"
• Cluster Environment: VirtualBox VMs + Vagrant
• Host OS: Ubuntu 18.04.5 LTS
• Linkerd version: stable-2.9.0

Possible solution

Additional context

[grampelberg]

It sounds like your ingress doesn't support websockets. You'll want to get that configured or just use port forwarding.

[donkodimov]

I am using nginx ingress. Websockets support is provided out of the box.
This annotation fixed my problem:

nginx.ingress.kubernetes.io/proxy-read-timeout: 3600
nginx.ingress.kubernetes.io/proxy-send-timeout: 3600

[kkcmadhu]

where did you apply this setting in the web-ingress of viz web?

[dewijones92]

@donkodimov where did you apply those settings please? thanks

[Samratmajumdar9748]

I'm also facing a similar issue. I'm using port forwarding in GKE but still getting this issue. Any ideas?